Skip to content

Conversation

yohanboniface
Copy link
Member

@yohanboniface yohanboniface commented Aug 15, 2025

fix #2843
fix #1570

Todo:

  • quick edit for filters from the browser
  • tests for undo/redo of field rename/delete
  • make filters orderable
  • find a way to edit the field type from the number edit form => add a link to go from filter to field and vice versa
  • adapt the input in the feature form according to the field type (if number, enum, date, etc.)
  • deal with parsing French dates (dd-mm-yyyy)
  • add a "field, filters and sort" fieldset
  • update widget list according to field type (do not show minmax for boolean, for example)
  • rename facet to filter in code and data (or vice-versa)
  • make filters work for boolean
  • add type=button on filters quick edit buttons
  • list datalayer AND map fields in the tableeditor
  • decide what to do when deleting a field with a related filter (delete filter or prevent deleting field?)
  • make clearer that there are fields on the map and on the layers (see Have a sense of deepness affordance for the side panel (+navigation!) #1156)
  • test for edit/rename where field exist both on datalayer and map

@yohanboniface yohanboniface force-pushed the enum-field-type branch 3 times, most recently from 7fd9b95 to 971e780 Compare August 22, 2025 14:54
@davidbgk davidbgk mentioned this pull request Sep 9, 2025
@yohanboniface yohanboniface force-pushed the enum-field-type branch 2 times, most recently from 7f0e474 to 3a5102f Compare September 17, 2025 14:11
yohanboniface and others added 23 commits September 22, 2025 19:03
Map will always respect the insertion order, so when updating
a field without rename it will update the existing entry, but when
the key changes, so it is like a new entry.
Co-authored-by: David Larlet <[email protected]>
Co-authored-by: David Larlet <[email protected]>
Co-authored-by: David Larlet <[email protected]>
davidbgk and others added 5 commits September 23, 2025 11:43
…nel (#2945)

fix #2927

CSS change is a bit violent, let's check that together :)
This created a bug when clicking on "Add a filter for this field",
which is calling "dialog.accept()" and then opening a new dialog.
In this case, the new dialog opens before the "close" event has
been sent, so it catches it wrongly.
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.

[Technical help] Filter keys pulled from multiple properties Multiple values for facet search
2 participants