-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: update graphql descriptions auth #3010
Conversation
- Added new descriptions for empty elements - Revised and refined existing descriptions
✅ Deploy Preview for brilliant-pasca-3e80ec canceled.
|
Add description for the query id argument
- Pagination - Filtering - Asset code
state: GrantState! | ||
"Reason a grant was finalized" | ||
"Reason why the grant was finalized." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a tough one, I kind of think "reason" is not the best usage here for the variable in general, I would say "outcome" or "status" is more accurate.
Could be: "The specific outcome for a finalized grant" or something like that. Not a blocker though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call on this one! I'd recommend renaming that variable (finalizationReason
) to not have "reason" in the name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, we can update it as part of a larger API change
actions: [String]! | ||
"Payment limits" | ||
"Limits for payment associated with this access." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Limits for payment associated with this access." | |
"Limits for an outgoing payment associated with this access." |
type: String! | ||
"Access action (create, read, list or complete)" | ||
"Actions allowed with this access (create, read, list, or complete)." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Actions allowed with this access (create, read, list, or complete)." | |
"Actions allowed with this access" |
There are more than those listed, and in different combination per each resource so safer to not mention I think
Changed a few descriptions per Max's PR feedback
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to merge once checks complete
Updated descriptions for the Auth Admin API. This fixes #2987
While these changes are enhancements to the current reference docs, I understand that the graphql schemas are also used to generate other files/types.