-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(filter): enable multi-selection filter #2173
Conversation
Deployed to https://pr-2173.aam-digital.net/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work already. Feels already very intuitive.
I only discovered one functional issue
- in roll call (record attendance) all options are pre-selected and entries without the property are not shown on default. I think this should just no create any filter object on default.
src/app/core/basic-datatypes/date/date-range-filter/date-range-filter.component.spec.ts
Outdated
Show resolved
Hide resolved
src/app/child-dev-project/notes/notes-manager/notes-manager.component.ts
Outdated
Show resolved
Hide resolved
I did a functional / UX review:
|
8995d09
to
e7144b8
Compare
e7144b8
to
bc71301
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for already integrating the things I pointed out. Functionality works very well. Only one more thing I discovered:
- default filter values in tasks and notes list are not working anymore. You can check at the deployed demo to see the difference
Generally, it would be very helpful if you don't overwrite your commits after a review has already been done. This way I don't know what new changes have been made to a file and there is no way of finding that out so I have to check the whole file again. Also locally I have to remove your branch locally to pull the updates.
src/app/core/basic-datatypes/configurable-enum/configurable-enum.service.ts
Outdated
Show resolved
Hide resolved
# Conflicts: # src/app/core/filter/filter.service.ts # src/app/core/filter/filter/filter.component.ts # src/app/core/filter/filters/filters.ts # src/app/features/todos/todo-list/todo-list.component.ts
REQUIRES MIGRATION
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the cleanups and tests. Looks great now. I did some smaller code changes, mostly unnecessary variables and usage of let
instead of const
when the variable is never re-assigned. We generally try to use const
as much as possible to prevent side-effects.
I have also removed a prebuilt filter from the NotesManagerComponent
as this can now be done with a normal filter on warningLevel
directly. We will need a small config migration for this though.
src/app/core/filter/filter-generator/filter-generator.service.spec.ts
Outdated
Show resolved
Hide resolved
src/app/core/filter/filter-generator/filter-generator.service.spec.ts
Outdated
Show resolved
Hide resolved
🎉 This PR is included in version 3.29.0-master.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 3.29.0-master.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 3.29.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
closes: #2075
Still some points open:
Visible/Frontend Changes
Architectural/Backend Changes