hierarchical track selector config options: collapse by default, sort ordering

[garrettjstevens]

@rbuels I decided to not actually do any configs for the track selector until the stuff you're working on now gets merged.

I was just planning to do some simple configs to have categories be expanded or collapsed by default. We could probably do a category and track sorting config sometime too, but not sure if we want to add that quite yet.

[rbuels]

draft config options that we would want initially:

• collapse sections by default (boolean)
• sort tracks and categories by name ascending/descending
• explicitly provide sort order of categories and tracks? how would we represent this in the config?

[cmdcolin]

I think we might want to renew this issue

The ordering is pretty arbitrary and based on ordering in config.json file. Should we implement something new?

[cmdcolin]

I believe the v1.1.0 has a default sort by name on categories but the virtualized tree removed this just for reference, resulting in slightly different observed ordering between v1.1.0 and v1.2.0 upcoming

[JoshuaFortriede]

Is there any update on this? It would be helpful to have more configuration on the track selector, specifically collapsing at category levels. It would also be good to have a defaultCollapse value and then collapse: {"Category_A":false"} to uncollapse specific categories.

[cmdcolin]

@JoshuaFortriede no updates on this yet but thanks for posting to add interest :) will try to see if we can get this worked in...

[anamariaelek]

An unexpected behavior I see here: it seems that the track that appears first (in any the category) in the config file ends up being the last one (in that category) in the track selector

[cmdcolin]

@anamariaelek is there any specific default behavior that you think might be best by chance? just asking cause we could try to make e.g. alphabetical sort on each category a default or e.g. "first that appears in config.json appears first in list" also

[AlbatrosHurleur]

@cmdcolin
I would vote for display order following config order :)

[anamariaelek]

I agree with @AlbatrosHurleur, having an option to modify this by changing the order in the config is really useful

[cmdcolin]

@anamariaelek @AlbatrosHurleur thanks for pushing forward with this issue. I made a PR here that may help to address #3808

can try it out the beta branch with jbrowse create --branch fix_track_ordering newinstance (or wait till next release! hopefully not too long)

[cmdcolin]

released in v2.6.3, some docs added here! https://jbrowse.org/jb2/docs/config_guides/track_selector/

[cmdcolin]

by default it should follow more or less the "order in the config.json" with the optional collapsing and alphabetical sorting documented there

[baeywen]

i upgraded to v2.6.3, and try to add the collapse feature into config.json following the docs, but it does not work in my test.
"configuration": {
"hierarchical": {
"sort": {
"trackNames": true,
"categories": true
},
"defaultCollapse": {
"topLevelCategories": true
}
}
},

[cmdcolin]

hi there, it is actually named "defaultCollapsed" and not "defaultCollapse". the docs are incorrect in a couple places on this so I will fix. hope that helps

[cmdcolin]

note also that the "defaultCollapsed" option are only applied when your session is first loaded, so you may need to clear the ?session= parameter from the URL bar for it to take effect

[baeywen]

hi there, it is actually named "defaultCollapsed" and not "defaultCollapse". the docs are incorrect in a couple places on this so I will fix. hope that helps

yes, this solved my problem. Thanks a lot!!