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.

Sign up for GitHub

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

Jump to bottom

Please don't break your API for an aesthetic change without going to v2... #127

Closed
yunginnanet opened this issue Apr 3, 2023 · 2 comments
Closed

Please don't break your API for an aesthetic change without going to v2... #127

yunginnanet opened this issue Apr 3, 2023 · 2 comments
Assignees
@arusso

Comments

@yunginnanet
Copy link

yunginnanet commented Apr 3, 2023 •
edited
Loading

We don't do this in go.

I'm sure you can see why.

This was not a good decision.
@arusso arusso self-assigned this Apr 3, 2023
@arusso
Copy link
Collaborator

arusso commented Apr 3, 2023

Agreed and sorry about the breakage.

@shomali11 and I have been discussing this and I'm working on documenting a release process to prevent this going forward.

@yunginnanet
Copy link
Author

Thanks for acknowledging, godspeed.

@arusso arusso mentioned this issue Apr 5, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arusso arusso

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@shomali11 @arusso @yunginnanet