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
As described in #851 "if a field has a YAML object as its content, it will not create a metadata record at all". Although there may be a valid reason for that, it is annoying that it implies that template conditions will not work properly on such fields.
Testing the existence of a field that contains complexe metadata can be really useful. Could it be possible to extend the template conditions to work with any fields in the YAML tree instead of only meta records'?
Hello,
As described in #851 "if a field has a YAML object as its content, it will not create a metadata record at all". Although there may be a valid reason for that, it is annoying that it implies that template conditions will not work properly on such fields.
Testing the existence of a field that contains complexe metadata can be really useful. Could it be possible to extend the template conditions to work with any fields in the YAML tree instead of only meta records'?
Below is an illustration:
Suppose a test.md file containing the following:
Suppose a test.plain template file containing the following:
Now lets process test.md with the custom test.plain template:
The output is the following:
Best,
Rémi
The text was updated successfully, but these errors were encountered: