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

Adopt AIP-0191 File and directory structure #46

Closed
makahmad opened this issue Oct 5, 2023 · 4 comments
Closed

Adopt AIP-0191 File and directory structure #46

makahmad opened this issue Oct 5, 2023 · 4 comments
Assignees
Labels
adoption adopting an AEP from aip.dev best-practices AEPs about API best practices

Comments

@makahmad
Copy link
Collaborator

makahmad commented Oct 5, 2023

No description provided.

@earth2marsh earth2marsh added the adoption adopting an AEP from aip.dev label Oct 11, 2023
@rofrankel rofrankel added the best-practices AEPs about API best practices label Jan 17, 2024
@toumorokoshi
Copy link
Member

this one is pretty proto-specific: should we put this into a "protobuf" section?

the HTTP transcoding AEP would also fit in this category.

@rambleraptor
Copy link
Member

I don't think this AEP is strictly necessary. There's a lot of Google-specific guidance in here (why do you need java_package_name but not go_package_name?) and none of it helps makes the APIs themselves any more intuitive / easy-to-generate.

@rofrankel
Copy link
Collaborator

@rambleraptor is going to drive discussion of whether we need this one.

@rambleraptor
Copy link
Member

Closed in #186

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
adoption adopting an AEP from aip.dev best-practices AEPs about API best practices
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants