Giters

Ecodev / natural

Angular Material components and various utilities

Home Page:https://ecodev.github.io/natural

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Decide how to treat orphan selections

sambaptista opened this issue · comments

commented

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)

  1. Invalidate selections (clear them)
  2. Consider selections are valid
  3. Invalidate selections when configuration is removed, but accept them if initialized without configuration ?
  4. 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

commented

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.