-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Changed endpoint star
to stars
#1603
Conversation
Generated by 🚫 dangerJS |
(Reopen of #1597) |
Careful, we have now deployed these badges, so there may be an impact on early users. 😉 |
@PyvesB I have noticed that today too! It's awesome that we have the badge ready now. Huge thanks to the team! And yes I will take responsibility for my code. 💪 |
I had spotted this complication. Given that if we merge this now, there's probably a few weeks between now and the next deploy, I think it would be better if the examples say Do you mind making that change @binhbbui411 - apologies for the bad timing |
@chris48s there are quite a few issues with the current deployment (see all the issues opened by @paulmelnikow in the past hours), so I suspect we might be deploying sooner than in a few weeks. Should we take that into account? |
The case `star` is the same as `stars`
@chris48s @PyvesB No problem, that makes sense as well. I have committed those changes. Also, we have only announced the badge to our internal staffs, so if you guys plan to make the next deploy in the next 2 weeks, I can postpone the announcement to our users and thus, accept only the endpoint |
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.
As it stands we can merge this and whether the next deploy is next few days or next few weeks, we minimise the chance of a breaking change. The additional overhead of supporting both endpoints is negligible so I'm inclined to go with both. I'm not strongly committed to that though: If we know there will be another deploy in the near future and nobody is using it yet, just changing it is fine.
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.
I agree with you we should support an old endpoint.
No description provided.