Filter model buttons do not work about substra-frontend HOT 5 CLOSED

A third solution that would work all the time could be to always filter on the traintuple key.

And we'd need this filter to apply to all "list" api endpoints. As a result, when a traintuple:key:xxxxx filter is applied, there should only be one challenge, one dataset and one algo listed in there respective tabs, and there should be at least one traintuple listed in the model tab (there may be more than one if there were inmodels listed for this traintuple).

This would introduce a small incoherence in the UI: the filter button on model pages creates a **traintuple**:key:xxxx filter, where users would expect a **model**:key:xxxx. However, as illustrated by the current issue, model:key:xxxxx doesn't work all the time unless xxxxxx is actually a traintuple key. But I'd rather have a small incoherence (model producing traintuple filter) than lying to the user (telling them it's a model key when it's really a traintuple key).

@camillemarini @GuillaumeCisco what do you think?

from substra-frontend.

waiting for @mattthieu input

from substra-frontend.

ping @mattthieu :-)

from substra-frontend.

This issue is almost 1 year old.
Is it still relevant?

from substra-frontend.

This has actually been solved. Filter buttons are now only displayed when relevant and the filter button works as expected.

from substra-frontend.