Bug 1181153: update to use the new treestatus API [DO NOT LAND] #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsantell
added a commit
that referenced
this pull request
Sep 23, 2015
Bug 1181153: update to use the new treestatus API [DO NOT LAND]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Untested, but a fairly straightforward change: URL changes, and the new API returns all results wrapped in an object with a "result" key.
Please don't land (well, don't ship) this until bug 1181153 gets deployed.
BTW, the
/treestatus/trees/{treename}endpoint is heavily cached and meant to be polled. I didn't try to fix that here, but if this extension is popular then that might help reduce unnecessary load.