-
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
Uncrispyfy DeviceGroupForm in seeddb #2994
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
008598a
Prepare edit form for uncrispyfying
podliashanyk 927bb84
Add template for form fields
podliashanyk 25ce6c1
Use non-crispy DeviceGroupForm in seeddb
podliashanyk a410bb8
Fix typo so that field errors can be rendered
podliashanyk 7fe2f74
Update python/nav/web/templates/seeddb/_form_fields.html
podliashanyk 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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
{% for field in form %} | ||
<div id="div_id_{{ field.name }}" | ||
class="ctrlHolder {% if field.errors %}error{% endif %}" | ||
podliashanyk marked this conversation as resolved.
Show resolved
Hide resolved
|
||
> | ||
<label for="id_{{ field.name }}" | ||
class="{% if field.field.required %}requiredField{% endif %}" | ||
> | ||
{{ field.label.title }} | ||
{% if field.field.required %}<span class="asteriskField">*</span>{% endif %} | ||
</label> | ||
{{ field }} | ||
{% for error in field.field.errors %} | ||
<small id="error_{{ forloop.counter }}_id_{{ field.name }}" class="error"> | ||
{{ error }} | ||
</small> | ||
{% endfor %} | ||
</div> | ||
{% endfor %} |
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
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
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.
When crispy is gone we will no longer need "no_crsipy" for choosing which form to show. It is still useful to hold extra form attributes though, like with the filter forms.
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.
Yes, we can remove
no_crispy = True
completely once all edit/add forms i seeddb are converted. Because then we can safely remove the{% if form.no_crispy %}
-block from theseeddb/edit.html
that was added in this PR and render{% include "seeddb/_form_fields.html" %}
by default there