-
Notifications
You must be signed in to change notification settings - Fork 212
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
Fix Lint issues in agoric-sdk #9632
Labels
Comments
toliaqat
added
enhancement
New feature or request
good first issue
Good for newcomers
labels
Jul 1, 2024
siarhei-agoric
added a commit
that referenced
this issue
Jul 11, 2024
siarhei-agoric
added a commit
that referenced
this issue
Jul 11, 2024
gibson042
added a commit
that referenced
this issue
Jul 11, 2024
gibson042
added a commit
that referenced
this issue
Jul 11, 2024
gibson042
added a commit
that referenced
this issue
Jul 12, 2024
gibson042
added a commit
that referenced
this issue
Jul 12, 2024
gibson042
added a commit
that referenced
this issue
Jul 12, 2024
gibson042
added a commit
that referenced
this issue
Jul 12, 2024
mergify bot
added a commit
that referenced
this issue
Jul 12, 2024
Ref #9632 ## Description * Fix bad JSDoc `@import`s * Make eslint-plugin-jsdoc aware of TypeDoc tags ### Security Considerations None; this PR only affects JSDoc comments. ### Scaling Considerations n/a ### Documentation Considerations Existing TypeDoc annotations are preserved and explicit support for currently-unused ones is added. ### Testing Considerations This should resolve all `Bad @import tag` and `Invalid JSDoc tag name` linter complaints. It currently upgrades [rule `check-tag-names`](https://github.com/gajus/eslint-plugin-jsdoc/blob/main/docs/rules/check-tag-names.md) violations to level "error" since we should not be using any unknown tags, but that could be relaxed if we find such configuration to be overly strict. ### Upgrade Considerations None.
gibson042
pushed a commit
that referenced
this issue
Jul 13, 2024
mergify bot
added a commit
that referenced
this issue
Jul 13, 2024
Ref #9632 ## Description Replaced `Array.forEach();` calls with `for ( x of y ) { };` loops. ### Security Considerations Assume that Array.forEach() calls are equivalent to `for ( x of y ) { };` in all cases. ### Scaling Considerations No significant difference expected. ### Documentation Considerations N/A ### Testing Considerations No new tests required. Local tests passed, including lint (specific to this PR). ### Upgrade Considerations The change preserves the behavior, thus there are no upgrade concerns.
siarhei-agoric
added a commit
that referenced
this issue
Aug 26, 2024
refs: #9965 Fixed the following two issues: 1. packages/inter-protocol/src/proposals/startPSM.js 351:1 warning Expected JSDoc block to be aligned jsdoc/check-alignment - factored out typedef from the type cast so the cast is now a single-line comment. 2. packages/agoric-cli/test/inter-cli.test.js 255:1 warning `test.todo()` should not be used ava/no-todo-test 361:1 warning `test.todo()` should not be used ava/no-todo-test 419:1 warning `test.todo()` should not be used ava/no-todo-test 610:1 warning `test.todo()` should not be used ava/no-todo-test 620:1 warning `test.todo()` should not be used ava/no-todo-test 622:1 warning `test.todo()` should not be used ava/no-todo-test 628:1 warning `test.todo()` should not be used ava/no-todo-test - Opened a new issue #9965 to creare missing tests and commented out test.todo()'s None None. None. None: passed lint and type checker; actual code not affected. None.
siarhei-agoric
added a commit
that referenced
this issue
Aug 27, 2024
closes: #3632 refs: #9965 Fixed the following two issues: 1. packages/inter-protocol/src/proposals/startPSM.js 351:1 warning Expected JSDoc block to be aligned jsdoc/check-alignment - factored out typedef from the type cast so the cast is now a single-line comment. 2. packages/agoric-cli/test/inter-cli.test.js 255:1 warning `test.todo()` should not be used ava/no-todo-test 361:1 warning `test.todo()` should not be used ava/no-todo-test 419:1 warning `test.todo()` should not be used ava/no-todo-test 610:1 warning `test.todo()` should not be used ava/no-todo-test 620:1 warning `test.todo()` should not be used ava/no-todo-test 622:1 warning `test.todo()` should not be used ava/no-todo-test 628:1 warning `test.todo()` should not be used ava/no-todo-test - Opened a new issue #9965 to create missing tests and removed test.todo()
siarhei-agoric
added a commit
that referenced
this issue
Aug 28, 2024
closes: #3632 refs: #9965 Fixed the following two issues: 1. packages/inter-protocol/src/proposals/startPSM.js 351:1 warning Expected JSDoc block to be aligned jsdoc/check-alignment - factored out typedef from the type cast so the cast is now a single-line comment. 2. packages/agoric-cli/test/inter-cli.test.js 255:1 warning `test.todo()` should not be used ava/no-todo-test 361:1 warning `test.todo()` should not be used ava/no-todo-test 419:1 warning `test.todo()` should not be used ava/no-todo-test 610:1 warning `test.todo()` should not be used ava/no-todo-test 620:1 warning `test.todo()` should not be used ava/no-todo-test 622:1 warning `test.todo()` should not be used ava/no-todo-test 628:1 warning `test.todo()` should not be used ava/no-todo-test - Opened a new issue #9965 to create missing tests and removed test.todo()
siarhei-agoric
added a commit
that referenced
this issue
Aug 28, 2024
closes: #3632 refs: #9965 Fixed the following two issues: 1. packages/inter-protocol/src/proposals/startPSM.js 351:1 warning Expected JSDoc block to be aligned jsdoc/check-alignment - factored out typedef from the type cast so the cast is now a single-line comment. 2. packages/agoric-cli/test/inter-cli.test.js 255:1 warning `test.todo()` should not be used ava/no-todo-test 361:1 warning `test.todo()` should not be used ava/no-todo-test 419:1 warning `test.todo()` should not be used ava/no-todo-test 610:1 warning `test.todo()` should not be used ava/no-todo-test 620:1 warning `test.todo()` should not be used ava/no-todo-test 622:1 warning `test.todo()` should not be used ava/no-todo-test 628:1 warning `test.todo()` should not be used ava/no-todo-test - Opened a new issue #9965 to create missing tests and removed test.todo()
siarhei-agoric
added a commit
that referenced
this issue
Aug 28, 2024
closes: #3632 refs: #9965 Fixed the following two issues: 1. packages/inter-protocol/src/proposals/startPSM.js 351:1 warning Expected JSDoc block to be aligned jsdoc/check-alignment - factored out typedef from the type cast so the cast is now a single-line comment. 2. packages/agoric-cli/test/inter-cli.test.js 255:1 warning `test.todo()` should not be used ava/no-todo-test 361:1 warning `test.todo()` should not be used ava/no-todo-test 419:1 warning `test.todo()` should not be used ava/no-todo-test 610:1 warning `test.todo()` should not be used ava/no-todo-test 620:1 warning `test.todo()` should not be used ava/no-todo-test 622:1 warning `test.todo()` should not be used ava/no-todo-test 628:1 warning `test.todo()` should not be used ava/no-todo-test - Opened a new issue #9965 to create missing tests and removed test.todo()
mergify bot
added a commit
that referenced
this issue
Aug 28, 2024
closes: #9632 refs: #9965 ## Description Fixed the following two issues: 1. packages/inter-protocol/src/proposals/startPSM.js 351:1 warning Expected JSDoc block to be aligned jsdoc/check-alignment - factored out typedef from the type cast so the cast is now a single-line comment. 2. packages/agoric-cli/test/inter-cli.test.js 255:1 warning `test.todo()` should not be used ava/no-todo-test 361:1 warning `test.todo()` should not be used ava/no-todo-test 419:1 warning `test.todo()` should not be used ava/no-todo-test 610:1 warning `test.todo()` should not be used ava/no-todo-test 620:1 warning `test.todo()` should not be used ava/no-todo-test 622:1 warning `test.todo()` should not be used ava/no-todo-test 628:1 warning `test.todo()` should not be used ava/no-todo-test - Opened a new issue #9965 to create missing tests and removed test.todo() ### Security Considerations None. ### Scaling Considerations None. ### Documentation Considerations None. ### Testing Considerations None: passed lint and type checker; actual code not affected. ### Upgrade Considerations None.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the Problem Being Solved?
Every PR shows some lint issue that we should cleanup. After fixing these Lint issues, we should force that no new lint issues are introduced.
Description of the Design
Security Considerations
Scaling Considerations
Test Plan
No lint warnings in the PRs.
Upgrade Considerations
The text was updated successfully, but these errors were encountered: