-
-
Notifications
You must be signed in to change notification settings - Fork 219
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
[B5] Support for migrating report views to Bootstrap 5 #35648
Merged
Merged
Changes from 1 commit
Commits
Show all changes
29 commits
Select commit
Hold shift + click to select a range
92dad95
add utils for bootstrap 5 paths
biyeun 1b593e9
add ability to set a report to use_bootstrap5
biyeun cef9291
pass use_bootstrap5 status to filters so the right template is chosen
biyeun eeb8ca5
create utility to get filter class individually
biyeun 850fa06
B5: add report debug tools and way to track completion
biyeun 9cca827
update bootstrap 5 migration guide for migrating report views
biyeun bb6a172
datatables_config (B5) - update how datatables gets imported
biyeun 74f5f6d
update datatables_config (B5) to work with datatables 1.10+
biyeun a357483
loading template no longer supported in datatables 1.10+
biyeun b57aa60
add todo about custom sort for future investigation
biyeun a859093
update how reports handles datatables server side params after 1.10
biyeun 3ff68d0
update the data returned by reports view to datatables
biyeun 6997dfc
update how sorting block in generated for datatables > 1.10
biyeun 2196bc7
update request parameter fetching for reports using Datatables 1.10+
biyeun 34b094d
Merge branch 'master' of github.com:dimagi/commcare-hq into bmb/b5-re…
biyeun 691d460
update method name to be clearer
biyeun b564d74
use get_bootstrap5_path on class variables that were missed
biyeun 8070d78
fix typo: progres > progress
biyeun 51da542
fix typo: list OF filters
biyeun 836c7e6
removing client-side custom sort overrides because datatables 1.10+ s…
biyeun 4ce3d85
add todo note aobut request_params versus request.GET
biyeun dd18ef4
split 'reports/async/basic.html' to bootstrap 3 and bootstrap 5 versions
biyeun 4820131
update bootstrap3 path to bootstrap 5 in reports/async/bootstrap5/bas…
biyeun b356d1e
switch between default_path templates for bootstrap 3 and 5 reports
biyeun 079d6a1
make sure DataTablesColumn has a bootstrap 5 version
biyeun 3362e88
migrate bootstrap 5 template for DataTablesColumn
biyeun 73ef95a
update sorting block to reference DataTablesColumn instance, as original
biyeun ca9c100
add column and sort checks to debug and completion tool
biyeun 7cca4df
"Bootstrap 5 Migration - Rebuilt diffs"
biyeun File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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'm assuming that
field
is currently only either a string or a class? If so, the parameter namefield
seems a bit misleading. Just making sure that we don't need to catch the possibility offield
being something else?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.
it's called
field
in the method it was extracted from. It only has that one use case, and the use case in our debug tools. no we don't need to catch other possibilities