-
Notifications
You must be signed in to change notification settings - Fork 284
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
Range filters should be improved to work mostly client side #2827
Conversation
a96896f
to
7fcbd6f
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.
This is going in the right direction, although I have a few suggestions/comments to look at please.
4761324
to
39b4a39
Compare
39b4a39
to
8361006
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.
I have one more comment here, and I think @maurofmferrao needs to review the JS please.
views/forms.twig
Outdated
<i class="fa fa-calendar"></i> | ||
</div> | ||
<input class="form-control dateControl date rangeInput" | ||
type="text" name="fromDt" id="fromDt" |
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.
Great, this reusable control is much better! Do we need to think about making the IDs here be specific to this control? If we include this macro more than once we will currently have duplicated IDs. The name would need to stay the same to it matches the API, but the ID could be unique to this instance (perhaps we could make the ID fromDt_name?)
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.
Hi, Dan! Thank you for this feedback! Please see updated changes here :)
c8fea00
to
ec9e3da
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.
This looks good to me, I'll leave it for Mauro to do the final review
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.
Just some minor changes regarding the code formatting, everything else looks great! 👍🏻
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.
Some more code formatting changes. 🙏🏻
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.
Looks good to me! ✅
@maurofmferrao how do you recommend this PR is tested? should the test wait until we've retargeted it to |
It might work for the |
TEST: /Reporting END |
Test Suite: failed ❌ |
TEST: /Reporting/report_timeconnectedsummary.cy.js END |
Test Suite: failed ❌ |
The cypress test of Time Connected Summary report needs to be updated to reflect the new changes. I am signing off on this work for now, and we will address the failed test later. |
TEST: login.cy.js END |
Test Suite: succeeded ✅ |
The base branch was changed.
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.
Looks good to me!
Changes
Relates to: xibosignage/xibo#2732