10
45
Fork
You've already forked doipjs
28

Enable linting of examples & tests #79

Open
vladimyr wants to merge 4 commits from vladimyr/doipjs:lint-everything into dev
pull from: vladimyr/doipjs:lint-everything
merge into: keyoxide:dev
keyoxide:main
keyoxide:dev
keyoxide:fix-irc-fetcher
keyoxide:new-claim-eveonline-143
keyoxide:prepare-new-release
keyoxide:fix-jsdoc-types
keyoxide:yarn-to-npm
keyoxide:support-openpgp-aspe-claims
keyoxide:support-html-alias
keyoxide:improve-activitypub-support
keyoxide:v1-restructure
keyoxide:into-es-module
keyoxide:support-aspe
keyoxide:fix-js-lsp-issues
keyoxide:improve-linting
keyoxide:add-markers
keyoxide:support-opencollective-claim
keyoxide:support-entity-decoding
keyoxide:use-rome-tools
keyoxide:support-cloudflare-buster
keyoxide:support-fediverse-posts
keyoxide:matrix-room-verification

Altering ESLint config so everything besides dist and docs is linted while ensuring correct treatment of Mocha tests.

Altering ESLint config so everything besides `dist` and `docs` is linted while ensuring correct treatment of Mocha tests.
Owner
Copy link

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

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
Ryuno-Ki left a comment
Copy link

Splendid!

Splendid!
@ -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)
Owner
Copy link

That could be another rule to add in a future PR: no-console.

That could be another rule to add in a future PR: no-console.
Author
Member
Copy link

Indeed 👍

Indeed 👍
Mocha has the [best reporter ever for local development](https://mochajs.org/#nyan) 😻
Author
Member
Copy link

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

Good idea, I'll diff old and new build output and paste results here.

> 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 Good idea, I'll diff _old_ and _new_ build output and paste results here.
vladimyr force-pushed lint-everything from a35b86c362
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
to cb1fd4a3b6
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
2024年02月02日 13:56:57 +01:00
Compare
vladimyr changed title from (削除) Enable linting of examples & tests (削除ここまで) to WIP: Enable linting of examples & tests 2024年02月02日 13:57:52 +01:00
Author
Member
Copy link

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.

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.
vladimyr changed title from (削除) WIP: Enable linting of examples & tests (削除ここまで) to Enable linting of examples & tests 2024年02月02日 21:34:51 +01:00

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).

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).
All checks were successful
ci/woodpecker/pr/test Pipeline was successful
This pull request has changes conflicting with the target branch.
  • 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.
git fetch -u lint-everything:vladimyr-lint-everything
git switch vladimyr-lint-everything
Sign in to join this conversation.
No reviewers
Labels
Clear labels
bug
Something is not working

Archived

enhancement
New feature

Archived

Contribution welcome
Get started contributing here
Good first issue
Good if you are new to the project or to open source contributions
Impact
External
Affects the people using the project
Impact
Internal
Affects on the people working on the project
Priority
Critical
Work on right now
Priority
High
Work on at earliest convenience
Priority
Low
Work on in spare time
Priority
Medium
Work on regularly
Review
Duplicate
Already exists
Review
Off Topic
Does not fall within the scope of the repo/project
Status
Backlog
Is not being worked on yet
Status
Blocked
Is waiting on something or someone
Status
Completed
Is done
Status
In Progress
Is being worked on
Status
Investigating
Is waiting on research or questions
Status
Needs Decision
Is waiting on a decision by the devs/contributors
Status
Needs Info
Is waiting on additional information before it can be solved
Status
Needs Triage
Is new issue that needs reviewing
Status
Testing
Is being checked and verified
Status
Waiting For Review
Is waiting on reviewers to approve
Status
Won't Fix
Won't be fixed
Type
Bug
Related to something not working as intended
Type
CI
Related to continuous integration
Type
Documentation
Related to documentation
Type
Enhancement
Related to a new feature or an improved one
Type
New Claim
Related to a new identity claim/proof
Type
Security
Related to security
Type
Tests
Related to code tests
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
keyoxide/doipjs!79
Reference in a new issue
keyoxide/doipjs
No description provided.
Delete branch "vladimyr/doipjs:lint-everything"

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?