-
Notifications
You must be signed in to change notification settings - Fork 15
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
Adopt AEP-122: Resource paths #63
Conversation
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.
thanks! a few comments to get the discussion going.
Also, as discussed this would actually be AEP 1022 (or some AEP 1*** number)? since it's in the "spec" portion of the AEPs? |
This is an adaptation of Roblox's AIP-122, which is an adaptation of Google's AIP-122. This primary difference from Google's AIP-122 is the change from "name" to "path" for the key concept defined by the AEP. Some notes on this PR: * This PR currently has protobuf-only guidance. If the content is generally acceptable to the working group, I'm happy to add the relevant OAS tabs. * The proposed new numbering scheme is ignored, because there are existing AEPs that don't use it. If and when we change the numbering scheme, a separate PR will be required anyway. * The PR uses apis.example.com/<api> (Roblox pattern) rather than "<api>.exampleapis.com" (Google pattern). No strong feeling about this either way.
Co-authored-by: Yusuke Tsutsumi <[email protected]>
Co-authored-by: Yusuke Tsutsumi <[email protected]>
f2ed60e
to
cb631aa
Compare
I think we converged on doing something with states instead, right? |
Co-authored-by: Yusuke Tsutsumi <[email protected]>
…nto resource-paths
@toumorokoshi any more comments on this? |
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.
one minor change it would be great to address, but otherwise approved!
Co-authored-by: Yusuke Tsutsumi <[email protected]>
* Adopt AEP-122: Resouce paths This is an adaptation of Roblox's AIP-122, which is an adaptation of Google's AIP-122. This primary difference from Google's AIP-122 is the change from "name" to "path" for the key concept defined by the AEP. Some notes on this PR: * This PR currently has protobuf-only guidance. If the content is generally acceptable to the working group, I'm happy to add the relevant OAS tabs. * The proposed new numbering scheme is ignored, because there are existing AEPs that don't use it. If and when we change the numbering scheme, a separate PR will be required anyway. * The PR uses apis.example.com/<api> (Roblox pattern) rather than "<api>.exampleapis.com" (Google pattern). No strong feeling about this either way. * Update aep/general/0122/aep.md Co-authored-by: Yusuke Tsutsumi <[email protected]> * Update aep/general/0122/aep.md Co-authored-by: Yusuke Tsutsumi <[email protected]> * Address PR feedback from @toumorokoshi. * Clarify wording around resource path uniqueness. * Add information about how to annotate valid ID formats. * Linkify `pattern`. * Update aep/general/0122/aep.md Co-authored-by: Yusuke Tsutsumi <[email protected]> * Address comments from @toumorokoshi. * Fix reference to JSON Schema keywords. * Add a slug to AIP-122. * Update aep/general/0122/aep.yaml Co-authored-by: Yusuke Tsutsumi <[email protected]> --------- Co-authored-by: Yusuke Tsutsumi <[email protected]> Co-authored-by: Yusuke Tsutsumi <[email protected]>
* Adopt AEP-122: Resouce paths This is an adaptation of Roblox's AIP-122, which is an adaptation of Google's AIP-122. This primary difference from Google's AIP-122 is the change from "name" to "path" for the key concept defined by the AEP. Some notes on this PR: * This PR currently has protobuf-only guidance. If the content is generally acceptable to the working group, I'm happy to add the relevant OAS tabs. * The proposed new numbering scheme is ignored, because there are existing AEPs that don't use it. If and when we change the numbering scheme, a separate PR will be required anyway. * The PR uses apis.example.com/<api> (Roblox pattern) rather than "<api>.exampleapis.com" (Google pattern). No strong feeling about this either way. * Update aep/general/0122/aep.md Co-authored-by: Yusuke Tsutsumi <[email protected]> * Update aep/general/0122/aep.md Co-authored-by: Yusuke Tsutsumi <[email protected]> * Address PR feedback from @toumorokoshi. * Clarify wording around resource path uniqueness. * Add information about how to annotate valid ID formats. * Linkify `pattern`. * Update aep/general/0122/aep.md Co-authored-by: Yusuke Tsutsumi <[email protected]> * Address comments from @toumorokoshi. * Fix reference to JSON Schema keywords. * Add a slug to AIP-122. * Update aep/general/0122/aep.yaml Co-authored-by: Yusuke Tsutsumi <[email protected]> --------- Co-authored-by: Yusuke Tsutsumi <[email protected]> Co-authored-by: Yusuke Tsutsumi <[email protected]>
This is an adaptation of Roblox's AIP-122, which is an adaptation of Google's AIP-122.
This primary difference from Google's AIP-122 is the change from "name" to "path" for the key concept defined by the AEP.
Some notes on this PR:
Addresses #55.