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

Ambiguity in Guidelines regarding scope syntax #135

Closed
Kevsy opened this issue Feb 6, 2024 · 2 comments
Closed

Ambiguity in Guidelines regarding scope syntax #135

Kevsy opened this issue Feb 6, 2024 · 2 comments
Labels
correction correction in documentation

Comments

@Kevsy
Copy link
Collaborator

Kevsy commented Feb 6, 2024

Problem description
Line 931 and 932 of Design Guidelines define scope syntax as follows:

  • (931) Use the kebab-case nomenclature to define API names, resources, and scope permissions.
  • (932) Recommended Format: <API_name>-<Resource>-<Permission>

Line 931 "kebab-case" implies lower kebab-case (also used in the image example following)
Line 932 implies Upper Snake case for API_name followed by Upper Kebab-case

Expected behavior
Line 932 to say:

Recommended Format: <api-name>-<resource>-<permission>

@Kevsy Kevsy added the correction correction in documentation label Feb 6, 2024
Kevsy added a commit to Kevsy/Commonalities that referenced this issue Feb 6, 2024
@Kevsy
Copy link
Collaborator Author

Kevsy commented Feb 6, 2024

Fixed in #136

@rartych
Copy link
Collaborator

rartych commented Feb 8, 2024

Closing as #136 is closed, and resolved within #57

@rartych rartych closed this as completed Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
correction correction in documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants