You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would love something that could leverage convention over configuration, e.g. look for a partial named with a pre-/postfix combined with the picked item's DocumentTypeAlias (or whatever the v8 equivalent is in code).
Kind of the way themes in UmbracoForms lets you override just a single FieldType's rendering.
(nice, a macro type setup without the clicks) so have file naming convention for a server side razor option and a textarea (save in property editor) for a client side option, or would that be better as file convention too ?
Activity
greystate commentedon Feb 28, 2019
I would love something that could leverage convention over configuration, e.g. look for a partial named with a pre-/postfix combined with the picked item's
DocumentTypeAlias(or whatever the v8 equivalent is in code).Kind of the way themes in UmbracoForms lets you override just a single FieldType's rendering.
Hendy commentedon Feb 28, 2019
(nice, a macro type setup without the clicks) so have file naming convention for a server side razor option and a textarea (save in property editor) for a client side option, or would that be better as file convention too ?
(dropping support for macros = no XSLT !)
greystate commentedon Feb 28, 2019
I think everything XSLT has been ripped from the guts of v8 anyway :)
Didn't even think of the client-side option, actually...
dawoe commentedon May 2, 2019
I think a client side label can't be done easily, because the datasource only returns the key and the label. So I don't see a real benefit from this.
I like greystates suggestion about a convention based partial location. That saves setting up the macro.
Dave