Skip to content
This repository was archived by the owner on Jan 8, 2025. It is now read-only.

Content field from _all.yml files are now loaded.#90

Open
jayvdb wants to merge 1 commit intothanethomson:masterfrom
jayvdb:pr_67_44c12a9b
Open

Content field from _all.yml files are now loaded.#90
jayvdb wants to merge 1 commit intothanethomson:masterfrom
jayvdb:pr_67_44c12a9b

Conversation

@jayvdb
Copy link
Collaborator

@jayvdb jayvdb commented Nov 17, 2018

This is 44c12a9 from #67 , fixed up to avoid test failures.

I've not attempt to built test cases yet, as I suspect a bit more code is needed.

No doubt the commit message is correct that it allows _all.yml entries to contain a Content field.

But then shouldnt individual entry .yaml files also be able to have a Content field. It looks like the code doesnt allow for that yet.

@PaulPichaureau
Copy link
Contributor

Individual files have an implicit Content field, which is in fact the content of the file (the part of the file after the header).

@jayvdb
Copy link
Collaborator Author

jayvdb commented Nov 18, 2018

Hiya @PaulPichaureau , I was referring to individual .yaml files - I suspect they are able to have a Content field, from only a quick look at the code. If that is true, then that needs to be added, but I suspect that is a really easy fix. Last night I wsa only wanting to split PR 67 into two chunks which could be separately reviewed, enhanced and completed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants