chore(deps): bump the biome group with 2 updates
Type: Pull Request
State: Open
Association: Contributor
Comments: 1
(4 months ago)
(4 months ago)
dependencies javascript
Bumps the biome group with 2 updates: @biomejs/wasm-nodejs and @biomejs/biome.
Updates @biomejs/wasm-nodejs from 2.1.2 to 2.1.3
Release notes
Sourced from @biomejs/wasm-nodejs's releases.
Biome CLI v2.1.3
2.1.3
Patch Changes
#7057
634a667Thanks@mdevils! - Added the rulenoVueReservedKeys, which prevents the use of reserved Vue keys.It prevents the use of Vue reserved keys such as those starting with
# @biomejs/biome (like$el,$data,$props) and keys starting with_` in data properties, which can cause conflicts and unexpected behavior in Vue components.Invalid example
<script> export default { data: { $el: "", _foo: "bar", }, }; </script><script> export default { computed: { $data() { return this.someData; }, }, }; </script>Valid examples
<script> export default { data() { return { message: "Hello Vue!", count: 0, }; }, }; </script>
... (truncated)
Changelog
Sourced from @biomejs/wasm-nodejs's changelog.
12.1.3
CLI
Other changes
rome lsp-proxyshould accept the global CLI options #4505- Enhance help descriptions
- Accept the environment variable 'ROME_BINARY' to override the Rome binary
Configuration
Other changes
- Fix an issue where all the
nurserywere enabled when the"nursery": {}object was defined #4479Formatter
Linter
Other changes
- Fix false positive diagnostics (#4483) that
useHookAtTopLevelcaused to returning call expressions of a hook.- Revert #4359
Parser
Other changes
- Revert #4359
Commits
018d188ci: release (#6927)ee4828dfeat(analyze/js): add useReactFunctionComponents rule (#7055)634a667feat(lint): implementnoVueReservedKeysrule (#7057)f75fea2refactor(format): use specialised tokens (#7052)c8f7838docs: update analyzer CONTRIBUTING.md (#7056)e5745c3ci: make it so windows devs don't get lints that don't show up on linux/macos...8b24337chore(deps): update rust:1.88.0-bullseye docker digest to b315f98 (#7043)b091ddffix(lint):useSemanticElementsself-closing elements (#7044)3fd5f73Revert "ci: use depot cargo in the PR workflow" (#7046)d0975f8ci: use depot cargo in the PR workflow (#7045)- Additional commits viewable in compare view
Updates @biomejs/biome from 2.1.2 to 2.1.3
Release notes
Sourced from @biomejs/biome's releases.
Biome CLI v2.1.3
2.1.3
Patch Changes
#7057
634a667Thanks@mdevils! - Added the rulenoVueReservedKeys, which prevents the use of reserved Vue keys.It prevents the use of Vue reserved keys such as those starting with
# @biomejs/biome (like$el,$data,$props) and keys starting with_` in data properties, which can cause conflicts and unexpected behavior in Vue components.Invalid example
<script> export default { data: { $el: "", _foo: "bar", }, }; </script><script> export default { computed: { $data() { return this.someData; }, }, }; </script>Valid examples
<script> export default { data() { return { message: "Hello Vue!", count: 0, }; }, }; </script>
... (truncated)
Changelog
Sourced from @biomejs/biome's changelog.
2.1.3
Patch Changes
#7057
634a667Thanks@mdevils! - Added the rulenoVueReservedKeys, which prevents the use of reserved Vue keys.It prevents the use of Vue reserved keys such as those starting with like
$el,$data,$props) and keys starting with\_in data properties, which can cause conflicts and unexpected behavior in Vue components.Invalid example
<script> export default { data: { $el: "", _foo: "bar", }, }; </script><script> export default { computed: { $data() { return this.someData; }, }, }; </script>Valid examples
<script> export default { data() { return { message: "Hello Vue!", count: 0, }; }, }; </script><script>
... (truncated)
Commits
018d188ci: release (#6927)ee4828dfeat(analyze/js): add useReactFunctionComponents rule (#7055)634a667feat(lint): implementnoVueReservedKeysrule (#7057)8f2703cchore: update generated code from analyzer codegen (#7001)0b1e194feat(json/analyze): rulenoQuickfixBiome(#6992)ab41f3fchore: fix changelog (#6917)- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions
Pull Request Statistics
0
0
+0
-0
Package Dependencies
Technical Details
| ID: | 4301859 |
| UUID: | 3274117763 |
| Node ID: | PR_kwDODeqQrc6hNDhv |
| Host: | GitHub |
| Repository: | acacode/swagger-typescript-api |