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

Use `null` in YAML instead of `nil` #2719

merged 1 commit into from Aug 10, 2014


None yet
3 participants

pathawks commented Aug 10, 2014

I believe that in YAML, null should be used rather than nil.

This is tricky because, in the Ruby source code, the values really are nil. That said, if somebody were to copy-paste the default config from the website, I believe that null is the most correct value to use.

If I am incorrect, or if this is a stylistic choice for Jekyll, please correct me and disregard this pull request.

parkr added a commit that referenced this pull request Aug 10, 2014

@parkr parkr merged commit 966b224 into jekyll:master Aug 10, 2014

1 check failed

continuous-integration/travis-ci The Travis CI build failed

This comment has been minimized.

Show comment
Hide comment

parkr Aug 10, 2014


You are correct! Thanks!


parkr commented Aug 10, 2014

You are correct! Thanks!

parkr added a commit that referenced this pull request Aug 10, 2014

@pathawks pathawks deleted the pathawks:null-not-nil branch Aug 10, 2014

noaxTheWanderer pushed a commit to noaxTheWanderer/ that referenced this pull request Sep 16, 2014

Noel Alex Makumuli Noel Alex Makumuli
Added new post for month of Agust
Using null instead of nill in atom.xml and rss.xml

@jekyll jekyll locked and limited conversation to collaborators Feb 27, 2017

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