Uh oh!
There was an error while loading. Please reload this page.
JCL-335: issue request builder & grant approval calls - #422
Conversation
acoburn
left a comment
There was a problem hiding this comment.
Might be worth discussing this in more detail
| * @param request an AccessRequest | ||
| * @return the next stage of completion containing the resulting credential | ||
| */ | ||
| public CompletionStage<AccessGrant> approveAccessRequest(final AccessRequest request) { |
There was a problem hiding this comment.
I would call this issueAccessGrant
There was a problem hiding this comment.
issueAccessRequest name is to specify it is a request and not the actual issue call.
I call it better issueGrantRequest
| /** | ||
| * An Access Grant issue request. | ||
| */ | ||
| public class AccessRequest { |
There was a problem hiding this comment.
I would have this extend or implement an AccessCredential type
| return this.data; | ||
| } | ||
| public AccessRequest(final Map<String, Object> data) { |
There was a problem hiding this comment.
I would make this more structured. A map is too general
timea-solid
commented
May 9, 2023
I know we discussed removing the extra class but that would require me to pass Map<String, Object> around. Because of this, I try here to create more architecture. |
acoburn
commented
May 19, 2023
Superseded by #461 |
The names are at the moment taken form the JS library:
We can of course rethink the names.
The issueAccessRequest has a toCompletableFuture().join() now, not sure.