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

Changed endpoint star to stars #1603

Merged
merged 3 commits into from
Apr 9, 2018
Merged

Changed endpoint star to stars #1603

merged 3 commits into from
Apr 9, 2018

Conversation

binbalenci
Copy link

No description provided.

@shields-ci
Copy link

shields-ci commented Mar 26, 2018

Messages
📖

✨ Thanks for your contribution to Shields, @binhbbui411!

📖

Thanks for contributing to our documentation. We ❤️ our documentarians!

Generated by 🚫 dangerJS

@paulmelnikow
Copy link
Member

(Reopen of #1597)

@paulmelnikow paulmelnikow added the service-badge New or updated service badge label Mar 27, 2018
@paulmelnikow paulmelnikow requested a review from chris48s March 27, 2018 04:03
@PyvesB
Copy link
Member

PyvesB commented Mar 27, 2018

Given this hasn't been deployed yet I think its reasonable to change the endpoint because every other service uses /stars as opposed to /star and there is no backwards-compatibility to break yet.

Careful, we have now deployed these badges, so there may be an impact on early users. 😉

@binbalenci
Copy link
Author

@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. 💪

@chris48s
Copy link
Member

Careful, we have now deployed these badges, so there may be an impact on early users

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 /stars but the regex/case statement accepts star|stars so we don't unexpectedly break badges for people who have adopted it in the meantime.

Do you mind making that change @binhbbui411 - apologies for the bad timing

@PyvesB
Copy link
Member

PyvesB commented Mar 27, 2018

@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?

Binh Bui added 2 commits March 27, 2018 21:07
The case `star` is the same as `stars`
@binbalenci
Copy link
Author

binbalenci commented Mar 27, 2018

@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 stars for the consistency. I would like to get a notice about that.

Copy link
Member

@chris48s chris48s left a 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.

Copy link
Member

@platan platan left a 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.

@chris48s chris48s merged commit e1755df into badges:master Apr 9, 2018
@binbalenci binbalenci deleted the star-to-stars branch April 9, 2018 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service-badge New or updated service badge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants