Allow skipSelect blueprints only when one blueprint exists #17818
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.
Since Umbraco 7.7 it has been possible to configure the behaviour when creating new content via AngularJS – to require the user to select a blueprint / content template, or auto-select one.
If
skipSelect
is enabled, the first available blueprint is selected. The issue has been if multiple blueprints exist for a specific type the user has no way to select which blueprint to use.This PR includes an additional check to only skip the content template select dialog if just one option exists – otherwise the user is presented a dialog to select.