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

Update API Design Guidelines fixes 135 (ambiguity in scope case) #136

Closed
wants to merge 1 commit into from

Conversation

Kevsy
Copy link
Collaborator

@Kevsy Kevsy commented Feb 6, 2024

Fixes #135

What type of PR is this?

Add one of the following kinds:

  • bug

What this PR does / why we need it:

Prevent ambiguity in scope syntax

Which issue(s) this PR fixes:

Fixes #135

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

@rartych
Copy link
Collaborator

rartych commented Feb 6, 2024

@Kevsy It seems the issue is fixed by PR #57

Please review it and close this PR if you approve proposed changes.

@Kevsy
Copy link
Collaborator Author

Kevsy commented Feb 6, 2024

Thanks @rartych , indeed it does. Closing this issue as fixed by #57

@Kevsy Kevsy closed this Feb 6, 2024
@Kevsy Kevsy deleted the patch-2 branch February 6, 2024 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ambiguity in Guidelines regarding scope syntax
2 participants