Fixes: #17459 - Ensure help text on component create forms shows both bulk edit and substitution token instructions #17931
Conversation
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
…it__ so it applies to all component types, and fix formatting
arthanson
previously approved these changes
Nov 4, 2024
jeremystretch
requested changes
Nov 15, 2024
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.
Fixes: #17459
This PR does two things:
Ensures that the
The string <code>{module}</code> will be replaced with the position of the assigned module, if any.string is shown on thenamefield of modular component create forms, in addition to theAlphanumeric ranges are supported for bulk creationstring, instead of the latter overwriting the formerMoves the
{module}help_text logic fromInterfaceCreateFormto the genericComponentCreateFormso that it applies to all modular device components which share the same bulk creation logic