-
Notifications
You must be signed in to change notification settings - Fork 3
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
Search allows filters with CreatedAfter greater than CreateBefore #2018
Comments
…ore (#2019) <!--- Provide a general summary of your changes in the Title above --> ## Description This PR disallows search filtering with `{dateProperty}After > {dateProperty}Before` for all available date filter types, * CreatedAt * DueAt * UpdatedAt * VisibleFrom (ServiceOwner only) Also adding tests to verify these filters work with normal use, and that validation errors are produced when the rule above is broken. ## Related Issue(s) - #2018 ## Verification - [x] **Your** code builds clean without any errors or warnings - [x] Manual testing done (required) - [x] Relevant automated test added (if you find this hard, leave it and we'll help out) ## Documentation - [ ] Documentation is updated (either in `docs`-directory, Altinnpedia or a separate linked PR in [altinn-studio-docs.](https://github.com/Altinn/altinn-studio-docs), if applicable)
Test🟢 Å lage et søk på før en tidlig dato samtidig som etter en sen dato gir nå en feilmelding siden det aldri vil gi treff EndUser + CreatedAtLegger ved detaljert eksempel med to søk et med riktig og et med feil datointervall som eksempel. CreatedAfter < CreatedBeforeCreatedAfter > CreatedBeforeEndUser + UpdatedAtOBSPostman er kilen på blankspaces "UpdatedAfter " != "UpdatedAfter" selv om vist URL i begge tilfeller blir den samme: |
This will always result in no results, since it makes no sense.
We "AND" these together, and a dialog cannot be created after 2023 and before 2022.
This applies to all date fields that can be filtered for both ServiceOwner and EndUser
The text was updated successfully, but these errors were encountered: