Altering ESLint config so everything besides dist and docs is linted while ensuring correct treatment of Mocha tests.
Enable linting of examples & tests #79
vladimyr/doipjs:lint-everything into dev
That's neat, makes a lot of sense to lint examples and tests too. I don't suppose it's possible to lint the JSDoc @example tags as well 👀 from a quick internet search, perhaps not
It's a pretty straightforward PR. Have you run yarn run build to check whether the builds still work? Hmm I suppose the CI should do that as well
@ -6,1 +4,3 @@
console.log(sp);
// const sp = doip.ServiceProviderDefinitions.data['activitypub'].processURI('https://fosstodon.org/@yarmo')
const sp = doip.ServiceProviderDefinitions.data.discourse.processURI('https://domain.org/u/alice')
console.log(sp)
That could be another rule to add in a future PR: no-console.
Indeed 👍
Mocha has the best reporter ever for local development 😻
It's a pretty straightforward PR. Have you run
yarn run buildto check whether the builds still work? Hmm I suppose the CI should do that as well
Good idea, I'll diff old and new build output and paste results here.
a35b86c362
cb1fd4a3b6
So here is what I did. First I built the library on the current dev branch and renamed dist to dist@dev. Then I switched to the branch behind this PR (lint-everything), created a new build, and compared the two:
$ git branch --show-current && diff -rs dist@dev dist
lint-everything
Files dist@dev/doip.core.js and dist/doip.core.js are identical
Files dist@dev/doip.core.min.js and dist/doip.core.min.js are identical
Files dist@dev/doip.fetchers.js and dist/doip.fetchers.js are identical
Files dist@dev/doip.fetchers.minimal.js and dist/doip.fetchers.minimal.js are identical
Files dist@dev/doip.fetchers.minimal.min.js and dist/doip.fetchers.minimal.min.js are identical
Files dist@dev/doip.fetchers.min.js and dist/doip.fetchers.min.js are identical
As you can see there are no changes in the build output so this should be ready and safe to merge.
Review is done. I updated to Completed Status to signify that it can be merged now (I don't have the permission to do so).
- examples/test-service-provider.js
- package.json
- yarn.lock
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Archived
Archived
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?