-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a new QueryParams model #859
Conversation
Trying to figure out those failures.. this is weird :( Adding [not ready] to title for now. |
Travis changed his mind when build was restarted. Weird stuff I saw locally was just a caching issue. OK to merge. |
Tests are passing 👍, will review once I get through e-mail backlog. |
defaults:{ | ||
stage:'all', | ||
state: 'open', | ||
page:1, |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
I say let's pull this in once you address the comments -- I admit I don't have the full picture of how this works in my head yet. Which means you volunteer to fix most of the bugs for |
Once #860 lands, I suggest rebasing and re-running grunt to catch the eslint errors. |
@hallvors want to fix the eslint errors then we can pull this in? |
4c5e4fc
to
5d8d32e
Compare
eslint saved me some real debugging there 👍 Anyway, the "push" build still has this failure:
But I don't get why.. adding some code that's not even used anywhere yet shouldn't cause failures, right? What's the "push" build anyway? |
Travis does two builds: push (when you push) and pr (if you make a pr). Your pr build passed, but the push one failed. I've seen that particular test fail in the past, so there's likely a bug somewhere. It seems to be somewhat random... so that's fun. 💣 |
Just retriggered the build (you can do that on Travis is you suspect weird results) and it's green now. Let's pull this one in. |
Add a new QueryParams model, #795.
This is just introducing a new QueryParams model. Nothing in this commit actually uses the new model yet, so if you want to test it you can only do so from the console:
etc..
(BTW: you first have to add a SCRIPT element to the DOM that actually loads the new code..
or something like that..)