Conversation
Add a property to the top-level Animation with structured fields (generator, author, description, keywords, theme color) and an open sub-property for arbitrary custom data. Includes schema, docs, examples, and valid/invalid test cases.
4055e91 to
cb3e62c
Compare
|
Do we need / want "theme color"? I'm not sure it's actually meta data |
@mbasaglia it's a very popular property |
| "x": { | ||
| "title": "Custom Metadata", | ||
| "description": "Object where authors can store any custom data. The contents of this property are not validated by the schema.", | ||
| "type": "object", | ||
| "additionalProperties": true | ||
| } |
There was a problem hiding this comment.
are we ok to name custom properties as x?
There was a problem hiding this comment.
I'd avoid x as it might interfere with expressions. IMO we can move away from single letter properties when we add stuff that is not already widely implemented
I believe it's because there's tooling that exports it but I don't like having rendering information in the metadata. |
Add an optional property to the top-level Animation with structured fields (g, a, d, k, tc) and an open sub-property for arbitrary author data. Includes schema definition, docs, examples, and valid/invalid test cases.
69752d8 to
a23e729
Compare
| animations. Implementations MUST NOT rely on any particular keys or structure | ||
| within `custom`. |
There was a problem hiding this comment.
Implementations MUST NOT rely on any particular keys or structure
I'm not sure I understand this statement
Summary
metaproperty to the top-level Animation objectwith structured metadata fields:
g(generator),a(author),d(description),k(keywords)custom(Custom Metadata) sub-property — an open object whereauthors can store any arbitrary data without schema constraints
composition.mdandhelpers.mdwith usage examples and implementation guidanceTest plan
docs/static/examples/metadata.jsonnpx jest)