Repository navigation
Emit priority data - #233
Merged
Merged
Conversation
Lukasa
force-pushed
the
emit-priority-data
branch
from
May 28, 2016 18:13
18baca0 to
bfbed52
Compare
Member
|
LGTM! Thanks for the fast response and implementation! 🎉 Should we also add Priority information upon receiving (i.e. generating a |
Member
Author
|
Yeah, probably. =D Let's use a new ticket. |
This file contains hidden or 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
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.
Resolves #229.
/cc @Kriechi
I'm a bit nervous about the fact that the kwargs are different in
send_headersandprioritize, but otherwise I think this is ok.