Skip to content

feat(filters): Add foundation + project and loc 1 filters - #203

Open
david-bretaud-dev wants to merge 6 commits into
david-bretaud-dev/prepare-filtersfrom
david-bretaud-dev/feat-filters-add-project-filter
Open

feat(filters): Add foundation + project and loc 1 filters #203
david-bretaud-dev wants to merge 6 commits into
david-bretaud-dev/prepare-filtersfrom
david-bretaud-dev/feat-filters-add-project-filter

Conversation

@david-bretaud-dev

@david-bretaud-dev david-bretaud-dev commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

Highlights

  • Add foundations to use filters in the frontend
  • Filters values are fetched/generated once from the backend, per layer
  • Add 2 fields to test the AND filtering: project and loc1
  • Implemented only the forest inventory card but make it easy to add the other layers/other fields

Debatable

Big question now: for now (and then), I'll apply filters per layer. E.G have project filter for each layer separately/independently. It's unclear whether it should be a global filter (to apply to all layers) or not.
For project it would make sense, but for loc1 for instance (which is a FK), it wouldn't since it's a FK value to a specific resource that has meaning only for a specific layer.

I put only checkboxes for now (+ support for date range), I don't know if users would rather a select.

Known issue

When applying filters, the cluster count is not recomputed => you can visualize the filter being applied only when the picto are displayed.

@david-bretaud-dev david-bretaud-dev self-assigned this Aug 20, 2026
@david-bretaud-dev david-bretaud-dev linked an issue Aug 20, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(filters): Add project filter

1 participant