Fixes #564 - fix history navigation from issues#603
Merged
Conversation
added 6 commits
February 27, 2015 16:54
on having to compute junk)
…y call Before per_page and sort were default params, this made sense. Now it doesn't.
Member
|
I can't deploy on my localhost (my MBA is .... not avalaibale :( ) hum there is some trouble with staging ? bad gateway ? |
Member
Author
|
Oh weird, let me debug. |
Member
Author
|
oops. |
Member
Author
|
OK, merged in master and deployed. There were some caching changes that this branch only had part of, so it exploded. Should be working now @magsout. |
Member
|
r+ |
magsout
added a commit
that referenced
this pull request
Apr 7, 2015
Fixes #564 - fix history navigation from issues
Member
Author
|
Thank you! |
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.
The problem was that I was creating an infinite
pushStateloop, more or less. Go back and push two more states on the history stack.This changes a bunch of things, but mostly it's a simplification. A lot less circular method calls.
I'm going to push this to staging so you can play around with it. I need to file one follow up issue that's unrelated to this bug, but is about
q=blahin the URL should be able to load that search in a fresh tab.r? @magsout