-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
[feature] Compound Filters (input & date) #32
Conversation
@jmzagorski Closes #26 |
I will review it today. Sorry I have been MIA on some of the tasks I said I was going to do this week. I had to rewrite many of my server Apis. |
No worries, I assumed you were busy, hence if you can't do it then I will merge it. No big issues. |
*/ | ||
destroy() { | ||
if (this.$filterElm) { | ||
this.$filterElm.off('keyup').remove(); |
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.
do you need a this.$selectOperatorElm.off('change')
here?
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.
oh right, I could do that one too.
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.
This looks real slick 👍, I was able to run it successfully in examples 4 and 5. I have one single comment for you to review and one general question: is your intention when the compound filter goes from a value such as =, >, < to blank that is defaults to equals?
Not always equals, it depends on the type. If it's a Type String it should be Contains for the rest it will be Equals |
oh okay I see, I did not test that out in example 5 on the |
Hmm I might have forgot to test that portion in a regular grid (without backend service), we should probably test it out in Example 4 or any other. I tested it in OData/GraphQL Backend Services and I have code to handle that. I think the regular grid are handled directly by their |
It's actually a good thing you talked about this since yes I forgot to test it with a regular grid and it is in fact not working correctly. I just fixed it in my Angular-Slickgrid repo with this commit. I will apply it to the Aurelia repo tonight. Or perhaps if you have time, I wouldn't mind if you do the changes that you mentioned and the fix for regular grid that I just talked about (on my branch). Or I can try to do them quickly during my lunch time in about 2 hours. |
I can look over your angular commit and see how to fix it. |
I assume that you are able to do the changes on the same branch right? It should be |
yup, I have it pulled down on my machine |
@ghiscoding |
Yup I try to re-use as much code as possible between the 2 repos 😄 EDIT I can update it myself tonight, unless you want to do it, here's the Angular commit |
- When using DatePicker with a TimePicker, we should simulate a user typing with delay to avoid too much backend traffic when chaging time
No description provided.