-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Query params for filters #347
Conversation
@@ -32,22 +32,23 @@ | |||
// TODO: first object should be a copy, otherwise one of the chart filters behaves different than the others. | |||
filters[filter.name] = filter; | |||
filters[filter.name].originFilters = []; | |||
if (_.has($location.search(), filter.friendlyName)) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about we use filter.name
? It has more chances to be more URL friendly (in most cases it's the table column name -> no capital letters and no spaces).
@arikfr Yeah, you are right, I thought that it will just be easy to create the url since the friendly name is right there when you want to create he deep link. Ofc name makes much more sense. Changed. |
Merged. @barnash congrats on your first contribution :-) |
@barnash two things I overlooked:
|
Cool, sounds good. On Tue Jan 20 2015 at 4:42:28 PM Arik Fraimovich notifications@github.com
|
I made it possible to register filters values in the query string - for dashboard view.
For example:
http://localhost:9001/dashboard/mydashboard?filter1=4&filter2=5