Skip to content
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

Documentation update #228

Merged
merged 1 commit into from
May 25, 2011
Merged

Documentation update #228

merged 1 commit into from
May 25, 2011

Conversation

akzhan
Copy link
Contributor

@akzhan akzhan commented May 25, 2011

Documentation update: Use GitHub syntax highlighting markup; 'default' is keyword, so use quotes; Other minor changes.

Previw update here: https://github.com/akzhan/jade/blob/master/Readme.md

…' is keyword, so use quotes; Other minor changes.
tj added a commit that referenced this pull request May 25, 2011
@tj tj merged commit c4c4179 into pugjs:master May 25, 2011

To alter the default simply change:

jade.doctypes.default = 'whatever you want';
```javascript
jade.doctypes['default'] = 'whatever you want';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you dont need this.. reserved words as props are fine

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

jslint fails on.

var data = {default: 'eek'};
$ jsl -process 1.js
JavaScript Lint 0.3.0 (JavaScript-C 1.5 2004-09-24)
Developed by Matthias Miller (http://www.JavaScriptLint.com)

1.js
~/1.js(1): SyntaxError: invalid property id
var data = {default: 'eek'};
............^


1 error(s), 0 warning(s)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

jslint doesn't matter lol it's not right

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Usually team coding standards require no errors and warnings of lint software. It's good practice.

But feel free to update ;)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

knowing the language is good practice :p not relying on outdated static analysis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants