-
Notifications
You must be signed in to change notification settings - Fork 46
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
feat: eslint #78
feat: eslint #78
Conversation
I was wondering how everyone else feels about a couple of things. There is a file added here So I was wondering how other people approach this. A second thing I noticed is that there appears to be a merge commit from master into this branch. Personally I would have rebased this branch on top of master, perhaps squashing some commits. But there may be reasons I am missing which would make that a bad idea. |
Adding eslint workflow for this project is a great idea. 👍 I'm not in favour of adding a |
.vscode settings giving a power of eslint and prettier on-save instead of only pre commit. I think this is awesome functionality in a price of one json file.. I see a lot of projects leveraging this |
ok, fair points. :-) If we do add {
"recommendations": [
"EditorConfig.EditorConfig",
"esbenp.prettier-vscode"
]
} |
Done |
@Jeroen-Matthijssens I will squash and merge this PR into master, so the commit into the main branch will be clean. I'm +1 on the VS Code stuff. It's relatively unobtrusive and I wouldn't propose adding anything for any other editors since I too use it exclusively. We can always change our minds. @vltansky can you fix the conflicts? I'll merge. |
ecmaVersion: 12, | ||
}, | ||
rules: { | ||
"no-console": "off", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pretty big one for this project
const packageName = "html5-boilerplate"; | ||
const tempDir = os.tmpdir() + `/${packageName}-staging`; | ||
const tempDir = `${os.tmpdir()}/${packageName}-staging`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@roblarsen fixed |
Thanks! |
🎉 This PR is included in version 0.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I forgot semantic-release. That's awesome- although since I forgot, it's not what I want from a communication perspective. That's not a feature that an end-user cares about at all so releasing a new version is silly. |
v0.3 released as this PR contained P.S |
Yeah, it's so cool to see it work. I just forgot about it when I bundled up your commit messages. We can manage it better in the future. No worries at all. |
Types of changes
Checklist:
This PR adds eslint configs (extends
eslint:recommended, airbnb/base, plugin:prettier/recommended
) - runnpm run lint
, lint workflow for PRs and VScode settings that enables eslint and prettier for the project by default