Decide how to treat orphan selections
sambaptista opened this issue · comments
Let's call selections without amatching configuration an orphan selection
.
What should NS do in those cases (actually case 1 is in place, but it's more like a default situation)
- Invalidate selections (clear them)
- Consider selections are valid
- Invalidate selections when configuration is removed, but accept them if initialized without configuration ?
- Configurable behavior ?
Other alternatives ?
All those alternatives could be followed by a new "search event" emission or not... ?
A possible usecase is when we have a specific configuration that is valid a single time, then if we refresh page, the selection stays valid, even if the configuration it initialized anymore https://support.ecodev.ch/issues/5786
It's been a long time since we created this. I assume that the status quo to silently ignore orphan selections is an acceptable behavior. And I am not aware of any needs that would require a different behavior.