Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Ruby-fied YAML files cause stack-trace #2

Closed
marksim opened this Issue Feb 7, 2012 · 3 comments

Comments

Projects
None yet
2 participants
Contributor

marksim commented Feb 7, 2012

<%
str_opts = "blah;blah;"
%>
opts: <% str_opts %>

Blows up when trying to parse the YAML file.

Owner

kindkid commented Feb 7, 2012

This looks like a can of worms to me.

I realize that there are some *.yml files living out there in config/ directories that are actually ERB files, but I find them ridiculous. They should probably have just been *.rb files instead.

Would it be sufficient for constantinople to simply skip yml files that it can't parse as YAML, and emit a warning when doing so?

Contributor

marksim commented Mar 1, 2012

I like this, but could there be a .ymlignore file which provided a list of files to skip in case we don't want constantinople to ever bother reading them?

@kindkid kindkid added a commit that referenced this issue Mar 1, 2012

@kindkid kindkid Merge pull request #3 from marksim/master
Additional Work for #2 to allow .constantinopleignore files to be loaded and ignore any path in them.
c37a49c
Owner

kindkid commented Mar 1, 2012

Thanks for the pull request. 0.2.2 released.

@kindkid kindkid closed this Mar 1, 2012

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