-
Notifications
You must be signed in to change notification settings - Fork 39
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
Remove fallback form rendering from uncrispified forms #3183
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
Test results 9 files 9 suites 8m 21s ⏱️ Results for commit 835e11c. ♻️ This comment has been updated with latest results. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3183 +/- ##
=======================================
Coverage 60.39% 60.39%
=======================================
Files 605 605
Lines 43701 43701
Branches 48 48
=======================================
Hits 26393 26393
Misses 17296 17296
Partials 12 12 ☔ View full report in Codecov by Sentry. |
50bfca2
to
de81e35
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.
Nice! See comments below.
And seems like self.attrs = set_flat_form_attributes()
is redundant in DeviceGroupForm
as well?
Yes, I believe we can remove calls to |
de81e35
to
835e11c
Compare
Quality Gate passedIssues Measures |
We decided that the template
web/templates/custom_crispy_templates/_form_content.html
has enough fallback by itselfFor more information see #3140 and #3157.