Introduced FieldData #81
Conversation
FieldData is an object nested inside an Entry's content.
Most implementation was on the client side, there's no FieldDataSchema in use right now because mongoose does not supported subdocuments outside of an Array. Having all FieldData in an array felt bad, what with not being able to access the data easily.
Every FieldData has a default `value` field inside its `data` object. This will contain default values. Future field types may populate the `data` object even further. Appropriate methods have been created.
User templates can still use `{{body}}` to access the value for a body. If however the Markdown plugin middleware is finished, templates can also start using `{{body_html}}`.
|
Hey @rubenvereecken — All seems fine, I didn't realize the inability to embed documents outside of an array :/ Just one small note on the Markdown field: I still think fields should be sandboxed to their slug. In the case of Markdown, I think the HTML should be the default, so |
|
Hmm so should the Field model have a method that defines how to extract values out of it? That would be a good approach. A Markdown Field would return its |
|
@rubenvereecken Yes, but this should be provided by the FieldType/plugin- |
2 participants
FieldData is an object nested inside an Entry's content.
Most implementation was on the client side, there's no FieldDataSchema in use right now because mongoose does not supported subdocuments outside of an Array. Having all FieldData in an array felt bad, what with not being able to access the data easily.
Every FieldData has a default
valuefield inside itsdataobject. This will contain default values. Future field types may populate thedataobject even further. Appropriate methods have been created.User templates can still use
{{body}}to access the value for a body. When the Markdown plugin middleware is finished, templates can also start using{{body_html}}.