Add header to the yaml files #9
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a header to the yaml files. For example, the header for a taskflow looks like this:
Because the header defines the file type, it means that we won't need to divide the taskflows, personalities, etc into separate directories, which will give us more flexibility in how the files are organized.
At the moment
main()still looks for top-level directories named "taskflows", "personabilities", etc. I'll remove that restriction in a separate PR.I've also included a version number in the header, because that might be useful in the future if we decide we want to change the file format.