ViewMeta
(Replacing message template with parser tag) |
(Updated Edited template to July 12, 2025.) |
||
(One intermediate revision by one other user not shown) | |||
Line 5: | Line 5: | ||
[[File:2018-07-21 11h12 53.png|none|thumb|1067x1067px]] | [[File:2018-07-21 11h12 53.png|none|thumb|1067x1067px]] | ||
The answer is an XML and does not divulge any sensitive information on implementation. It merely states names, suggested placement, suggested control type, and labels. | The answer is an XML and does not divulge any sensitive information on implementation. It merely states names, suggested placement, suggested control type, and labels. | ||
==== Blazor ==== | |||
Since Blazor is a client side framework - the client will need full meta information in order to build the ui. For this purpose a new per view meta controller has been added: | |||
http://<YourSite>/Turnkey/ViewMetaBlazorClient?view=NameOfViewModel | |||
[[Category:MDriven Turnkey]] | [[Category:MDriven Turnkey]] | ||
{{Edited|July|12| | {{Edited|July|12|2025}} |
Latest revision as of 06:24, 20 January 2025
This page was created by Hans.karlsen on 2018-07-21. Last edited by Edgar on 2025-01-20.
Turnkey offers metadata on a per-view basis to support advanced component development and complete new front-end implementation.
See: http://<YourSite>/Turnkey/ViewMeta?view=SampleViewModel
The answer is an XML and does not divulge any sensitive information on implementation. It merely states names, suggested placement, suggested control type, and labels.
Blazor
Since Blazor is a client side framework - the client will need full meta information in order to build the ui. For this purpose a new per view meta controller has been added:
http://<YourSite>/Turnkey/ViewMetaBlazorClient?view=NameOfViewModel