-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Pick macro parameters in an infinite editor like content type properties #6586
Pick macro parameters in an infinite editor like content type properties #6586
Conversation
…r to select parameter editor.
Thanks @bjarnef, we'll have a look! Adding descriptions and group names to the |
@nul800sebastiaan yes, the property editors also use a I think we can start with this and enhance it later. Furthermore I don't think we need to request macro partial views when loading a macro, but we can change this in another PR. |
This is lovely work @bjarnef! Many thanks, it all works wonderfully! ⭐️ 💪 |
…ton (#6561) * Improves accessability of the three dot tree options button * Updated list view headers styling to have the link/hand cursor visible only if the header is sortable (and hence clicking has an effect) * Allows members to be ordered by additional system fields (#6575) * Fix ContentType.Alias matching in PublishedContentExtensions an… (#6577) * Fixes an error in #6538 by moving the colon character to the sr-only span * V8: Move misplaced colon in language selector (#6692) * V8: It should be possible to disallow all types at content root (#6580) * Pick macro parameters in an infinite editor like content type properties (#6586) * Reload node children after publishing with descendants * Correct URL decoding of macro partial view names (#6592) * Fix semantics for list views (#6595) * fixes test * fixing tests * Improved menu context
Prerequisites
If there's an existing issue for this PR then this fixes #4318
Description
This PR adjust to macro parameters to be more consistent with manage properties and their datatypes on document types, media types and member types.
It also don't request parameter editors, before you want to edit or add a parameter.
At the moment the parameters doesn't have info about the "datatype name", so it make a request here. Not sure if it is easy to extend the
MacroParameterDisplay
with aDataTypeName
or similar property here?https://github.com/umbraco/Umbraco-CMS/blob/v8/dev/src/Umbraco.Web/Editors/MacrosController.cs#L119-L125
It would be great if the macro parameters also supported description as well, so you can add a description like on properties for document, media and member types.