Lineage comparison page: changing lineages from "already selected" should not trigger API calls
flaneuse opened this issue · 1 comments
flaneuse commented
On the lineage comparison page, when you add/remove/clear lineages, the API calls should not be triggered until you click "create report".
The behavior is correct if you add a lineage but not if you remove/clear a lineage.
Have the changes from the current main branch been incorporated? I know we fixed this before.
olekkorob commented
As I checked, we don't trigger API call when we add/remove/clear lineages. Only route is changing.