![]() id: A unique identifier for the layout a.k.a.columns: A two dimensional array where each inner array represents a macro-column, and each item in the inner array is a row identifier.Type: Layouts is an array of layout objects.Ī layout MUST contain at least the following top-level members: Layouts collect rows and organize them in macro-columns. template: A template object that contains information about the structure of the page outside of the form in the renderer i.e.actions: An action object that contains information about the population of form buttons in the renderer.fields: An object of fields keyed by the fieldId.Ī document MAY contain any of the following top-level members:.This object defines a document’s “top level”.Ī document MUST contain at least the following top-level members: Top LevelĪ JSON object MUST be at the root of every metadata document. Client implementations MUST ignore members not recognized by this specification. Unless otherwise noted, objects defined by this specification MUST NOT contain any additional members. Metadata documents are defined in JavaScript Object Notation (JSON). This section describes the content of a metadata document. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119. The metadata API will not enforce the method by which it is rendered. ![]() The metadata API is designed to abstract the development of CRUD forms away to a specification of its parts, leaving the layout to a rigidly enforced design system or other renderer. Metadata is a JSON object that provides an abstract specification of UI forms both in their included elements and layout. In addition to the actual version being in flux, the official name of this specification outside of “metadata” has neither been decided nor discussed. The expectation is that the metadata will follow Semantic Versioning and track changes to the spec in a manner that conforms to Keep a Changelog. The current approach to versioning is still under debate, specifically what is considered a version 1 (the current specification is pre-v1).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |