-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider new YAML format standard #418
Comments
@ryansb I think the change you suggested would fit well into the code. I also know that it would help clean up some more "sloppy" lines of code I was forced to write. @decause what are your thoughts on making the YAML files each simply a dictionary? |
+1 to simple dictionary. Originally the .yaml was adapted from a giant Simple dictionary yes. On Tue, Aug 12, 2014 at 3:05 PM, Liam Middlebrook notifications@github.com
Remy DeCausemaker Rochester Institute of Technology |
See #421 |
#423 adds the final changes for this issue to be completed. |
Closing this out, new yaml format merged in. |
Current YAML:
New yaml suggested by @liam-middlebrook in #416
I like this change, but I have a couple suggestions.
First, the format extracts as
[{"blog": "...", "otherthing": "...}]
. I'd like to get rid of theAnd instead just have the format extract as a dictionary like
{"blog": "...", "name": "...."}
As an added bonus, every line wouldn't need a 2-space indentation.
The text was updated successfully, but these errors were encountered: