-
Notifications
You must be signed in to change notification settings - Fork 5
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
Ab#79314 add filters tooltips #837
base: beta
Are you sure you want to change the base?
Conversation
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.
@MwanPygmay While checking the date type issue on the front end, you could also combine here in the backend the cases of 'numeric', 'date' and 'time' fields since they have the same code and we can just send the data string to the frontend once since datepipe already converts it to date when necessary
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.
Working as expected.
Description
Wrote query to get fields details. Query should be optimised: the max records that we query is 5. Sort and limit should behave well and avoid sorting the whole records (see documentation below). Would be good to test on a database with lots of records. On small database it is instant.
Useful links
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
See front, acquirement of data went well. Main problem is often not providing a resource id.
Screenshots
See front.
Checklist:
( * == Mandatory )