You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Master issue for the refactor of record filters and record sorts.
Goals of this refactor :
Remove component state v1 from record filter and record sort states.
Progressively rollout a V2 handling of record filters and record sorts that is acting in parallel, so we only have to switch to V2 from V1 without breaking anything
Have record filters and record sorts act as standalone modules and also standalone contexts, that can be used by other related modules : index, table, kanban, view, context store.
ViewFilter and RecordFilter are two concepts that are used in the view module.
They are required to keep the database ViewFilter concept and the UI Filter concept separated, but right now we could have a better abstraction of ViewFilter.
Because in the UI we manipulate almost always RecordFilters, and we could have it turned into ViewFilter and back again so that we never manipulate ViewFilter directly.
@FelixMalfait@ad-elias I'll take it because we need to be very precise about it with @charlesBochet and we already discussed implementation details, also I'll be refactoring related things this sprint.
Master issue for the refactor of record filters and record sorts.
Goals of this refactor :
ViewFilter and RecordFilter are two concepts that are used in the view module.
They are required to keep the database ViewFilter concept and the UI Filter concept separated, but right now we could have a better abstraction of ViewFilter.
Because in the UI we manipulate almost always RecordFilters, and we could have it turned into ViewFilter and back again so that we never manipulate ViewFilter directly.
The text was updated successfully, but these errors were encountered: