Fix storage asset form validation error - #514
Merged
Merged
Conversation
paulapreuss
marked this pull request as ready for review
September 1, 2026 13:49
paulapreuss
force-pushed
the
fix/toggle-fields
branch
from
September 1, 2026 13:54
72ce96c to
d0c2fbe
Compare
paulapreuss
force-pushed
the
fix/toggle-fields
branch
from
September 1, 2026 14:04
d0c2fbe to
dc1b0b4
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The optimize capacity toggle fields introduced in #487 caused an error due to the same logic not being applied to the storage asset template form. Upon further investigation, the asset_create_form and the specific template for storages were near duplicates, causing issues with divergence when only one of them was updated. I have now deleted the specific storage template and handled the differences with
{% ifblocks directly in the template.