Understanding what is(not) available in configuration features #7184
mp3monster
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Some features within the traditional configuration are not possible with the YAML options. It might be worth providing a document which shows which features are (not)available in one format both the other with a link to the associated documentation.
e.g. traditional format allows @inclcude and @set but there isn't a YAML equivalent.
This would help people assess what might be involved in switching or deciding which format to adopt
thoughts?
Beta Was this translation helpful? Give feedback.
All reactions