Since we filter on slug only and return ID only, it's a royal PITA to make sure we use slugs in some places and IDs in others. Can we choose one?
https://github.com/mozilla/zamboni/pull/1082 (bug 911382) will allow you to filter on ids in addition to slugs. We could still return slugs if you prefer though.
There's only a few places left that we use IDs, so I'd rather just get rid of those places than convert everything back from slugs. Slugs make for nicer URLs, as well.
Ok, I'll take a stab at this.
Assignee: nobody → mpillard
Priority: -- → P3
Target Milestone: --- → 2013-09-10
Fixed in https://github.com/mozilla/zamboni/commit/e2e71c7579fc1ef0f32de896c0c2d6b7f453fcdf Since this is a backwards-incompatible change, someone will need to update rocketfuel to fix the resulting temporary breakage, this is bug 913003
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Guys, this breaking change could have resulted in service our breakage (everything.me). Luckily we previewed the dump in a local computer and witnessed the breakage before the production update. We need to be notified on every breaking change. What do we need to do to make this happen? Btw, the api documentation doesn't reflect the change either.
Typo in first line: ...breakage in our service
Ran: are you using a rocketfuel API endpoint? Those endpoints are designed specifically for consumption by a tool of ours and aren't guaranteed to be stable, per the note at the top of the page in the docs here: http://firefox-marketplace-api.readthedocs.org/en/latest/topics/rocketfuel.html If this fix broke something outside of those endpoints, would you mind filing a bug about it? That would be a pretty high-priority problem. Thanks!
Hey Chuck, no we're using the official v1 api. Here's an example of the change on production. I'll open a bug. https://marketplace.firefox.com/api/v1/apps/app/twitter/?format=JSON
Created Bug 932365
(In reply to Ran Ben Aharon (Everything.me) from comment #9) > Created Bug 932365 Thanks Ran. Sounds like this affected more APIs than planned for.
You need to log in before you can comment on or make changes to this bug.