Skip to content

Conversation

jimabramson
Copy link

XCOM-208

@clintonb @rlucioni please review. The first commit will go away when #2 is merged.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling c8012d7 on jsa/xcom-208 into * on master*.

@clintonb
Copy link
Contributor

clintonb commented May 1, 2015

@jimabramson My rebasing for #2 threw things out of whack. Rebase on master, and we should be good to go.

@clintonb
Copy link
Contributor

clintonb commented May 1, 2015

👍

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling cf398e7 on jsa/xcom-208 into 423f634 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 039e541 on jsa/xcom-208 into 423f634 on master.

@rlucioni
Copy link

rlucioni commented May 4, 2015

If tracking_context remains a dictionary over in #80, 👍. If the JWT payload is kept flat, please update this accordingly.

@rlucioni
Copy link

rlucioni commented May 4, 2015

I think this change warrants incrementing the version number in setup.py.

jimabramson pushed a commit that referenced this pull request May 5, 2015
support tracking_context in jwt token.
@jimabramson jimabramson merged commit 8eaa06e into master May 5, 2015
@jimabramson jimabramson deleted the jsa/xcom-208 branch May 5, 2015 02:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants