Skip to content

generator: Consider removing @BetaApi from client HTTP JSON surface #2101

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

Closed
burkedavison opened this issue Oct 11, 2023 · 3 comments · Fixed by #2358
Closed

generator: Consider removing @BetaApi from client HTTP JSON surface #2101

burkedavison opened this issue Oct 11, 2023 · 3 comments · Fixed by #2358
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@burkedavison
Copy link
Member

@burkedavison burkedavison added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Oct 11, 2023
@JoeWang1127 JoeWang1127 self-assigned this Jan 4, 2024
@JoeWang1127
Copy link
Collaborator

Hi @burkedavison, I picked up this issue from backlog. Are the three examples the only places you want to remove the BetaApi annotation?

@burkedavison
Copy link
Member Author

This ticket asks to "Consider" removal, so working with @blakeli0 to determine the impact of removing the annotation and making a firm decision before doing so.

The actual implementation of the removal is likely just those 3 places.

@JoeWang1127
Copy link
Collaborator

@blakeli0 confirmed that we're good to fix this issue. Also, removes BetaApi annotation even if the package name is alpha or beta.

JoeWang1127 added a commit that referenced this issue Feb 15, 2024
ddixit14 pushed a commit that referenced this issue Feb 15, 2024
lqiu96 pushed a commit that referenced this issue Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants