Thanks to visit codestin.com
Credit goes to github.com

Skip to content

replace == with === #91

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

Merged
merged 1 commit into from
Jan 10, 2017
Merged

replace == with === #91

merged 1 commit into from
Jan 10, 2017

Conversation

vsemozhetbyt
Copy link
Contributor

(Here comes a bunch of PRs after a code fragments mass test with ESLint checks and Node.js runnings.)

(This commit also deletes a redundant else.)

@ryanmcdermott ryanmcdermott merged commit fcfab4e into ryanmcdermott:master Jan 10, 2017
@ryanmcdermott
Copy link
Owner

Lint lint lint!

@ryanmcdermott
Copy link
Owner

ryanmcdermott commented Jan 10, 2017

By the way, do you use any tool to connect ESLint to code sections in a Markdown file in order to lint it?

@vsemozhetbyt vsemozhetbyt deleted the eqeqeq branch January 10, 2017 07:50
@vsemozhetbyt
Copy link
Contributor Author

vsemozhetbyt commented Jan 10, 2017

@ryanmcdermott No :) I've just deleted the text before the first and after the last code, then I've replaced all text between code fragments by comment signs like this:

text.replace(
  `/```[\s\S]+?```javascript/`,
  `*******************************************************************************/
/*******************************************************************************`
);

Then I've added the appropriate comment sign in the first and the last lines. And then I've linted and run each fragment uncommentig them one by one)

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