-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
[Code Inspection] Data Cleaning Prototype (HTMX + Alpine) #34846
base: master
Are you sure you want to change the base?
Conversation
🔍 Existing Issues For ReviewYour pull request is modifying functions with the following pre-existing issues: 📄 File: corehq/apps/hqwebapp/templatetags/hq_shared_tags.py
Did you find this useful? React with a 👍 or 👎 |
…atedTableView as base view
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.
Why is this custom loading logic needed? It seems to do the same thing as hx-indicator
: https://htmx.org/attributes/hx-indicator/
hx-swap="outerHTML" | ||
hq-hx-refresh="{{ table_selector }}"> |
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.
why are these on the div? I expected to see them on the same element that's making the request.
hx-post="{{ request.path_info }}{% querystring %}" | ||
hx-disable-elt="this" | ||
hq-hx-loading="{{ table.loading_indicator_id }}" | ||
hx-on::after-request="htmx.trigger('#{{ table.column_manager.filter_form_id }}', 'refreshFilters');"> |
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 seems to duplicate the hq-hx-refresh
functionality. Do we need both?
Product Description
Technical Summary
Feature Flag
Safety Assurance
Safety story
Automated test coverage
QA Plan
Migrations
Rollback instructions
Labels & Review