Skip to content
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

Merged
merged 6 commits into from
Oct 15, 2024

Conversation

brad-dow
Copy link
Contributor

@brad-dow brad-dow commented Oct 1, 2024

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.

- Added new descriptions for empty elements
- Revised and refined existing descriptions
@brad-dow brad-dow requested a review from mkurapov October 1, 2024 21:09
@github-actions github-actions bot added type: source Changes business logic pkg: auth Changes in the GNAP auth package. labels Oct 1, 2024
Copy link

netlify bot commented Oct 1, 2024

Deploy Preview for brilliant-pasca-3e80ec canceled.

Name Link
🔨 Latest commit c8dc437
🔍 Latest deploy log https://app.netlify.com/sites/brilliant-pasca-3e80ec/deploys/670e852c5939b10009f3b3b2

Add description for the query id argument
- Pagination
- Filtering
- Asset code
state: GrantState!
"Reason a grant was finalized"
"Reason why the grant was finalized."
Copy link
Contributor

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

Copy link
Contributor Author

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.

Copy link
Contributor

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."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"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)."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"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
@brad-dow brad-dow changed the title Docs update graphql descriptions auth docs: update graphql descriptions auth Oct 14, 2024
Copy link
Contributor

@mkurapov mkurapov left a 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

@brad-dow brad-dow merged commit ba7045f into main Oct 15, 2024
25 of 26 checks passed
@brad-dow brad-dow deleted the docs-update-graphql-descriptions-auth branch October 15, 2024 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkg: auth Changes in the GNAP auth package. type: source Changes business logic
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Docs: Add and revise field descriptions in Auth Admin API GraphQL schema
2 participants