You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Permalinks on Evolution dashboard do not retain selected aggregates for categorical histogram #395
changed the title [-]Permalinks on Evolution dashboard do not retain selected keys for keyed histogram[/-][+]Permalinks on Evolution dashboard do not retain selected aggregates for categorical histogram[/+]on Feb 13, 2018
@chutten i have gone through the issue and i think the selected aggregate type is not part of the url which is used to restore state of the page. Is it something you are working on or shall i work on this issue
I also don't get what's going on here, it seems like the aggregates key have nothing to do with the applicable values.
This is pretty weird indeed ! :)
I should probably also file a (maybe) followup bug because it seems like I have to click on the aggregate selector twice before it selects anything O_o
Activity
[-]Permalinks on Evolution dashboard do not retain selected keys for keyed histogram[/-][+]Permalinks on Evolution dashboard do not retain selected aggregates for categorical histogram[/+]chutten commentedon Feb 13, 2018
Probably fallout from #377 where I reworked how we load and change measures in the evo dashboard.
ab0092 commentedon Feb 23, 2018
@chutten i have gone through the issue and i think the selected aggregate type is not part of the url which is used to restore state of the page. Is it something you are working on or shall i work on this issue
o0Ignition0o commentedon Feb 25, 2018
It seems like the aggregates are part of the url, eg : "http://0.0.0.0:8000/new-pipeline/evo.html#!aggregates=0!4" but they don't get parsed the right way.
I also don't get what's going on here, it seems like the aggregates key have nothing to do with the applicable values.
This is pretty weird indeed ! :)
I should probably also file a (maybe) followup bug because it seems like I have to click on the aggregate selector twice before it selects anything O_o
chutten commentedon Feb 26, 2018
Oh geez, the aggregates are saved to the URL using their index? That's... probably "mostly fine" but certainly isn't parsed that way.
gargshruti30 commentedon Mar 21, 2018
@chutten @georgf Can I work on this issue ?
chutten commentedon Mar 21, 2018
Yes you may. It might prove tricky. You may want to start by looking at #404 and at the code in
loadStateFromUrlAndCookie