Boshen
c0e9616fe7
Release oxlint v0.0.16, vscode extension v0.0.16
2023-11-08 11:40:46 +08:00
Boshen
9b913301e8
chore(editor/vscode): remove unused dependencies and also webpack.config.js ( #1153 )
2023-11-05 21:09:34 +08:00
Boshen
f7c4abe84c
Release vscode extension v0.0.3
2023-11-05 15:05:32 +08:00
Boshen
5aa7cc1718
publish vscode ( #1144 )
2023-11-05 15:03:22 +08:00
ubugeeei
f75485b41f
add icon file for vscode extension ( #1134 ) ( #1135 )
...
Closes #1134
I'm not sure if it's the correct solution, but I solved it this way, so
I'll submit a PR. As for the icon, I took it from the marketplace.
https://marketplace.visualstudio.com/items?itemName=oxc.oxc-vscode
2023-11-04 08:42:18 +08:00
Boshen
223877b6fd
feat(vscode): prepare for publish ( #1123 )
2023-11-01 09:49:29 +08:00
Boshen
a9b85b60b1
chore(vscode): disable the "run all" as it is disruptive ( #1122 )
2023-11-01 09:41:56 +08:00
Boshen
5a44c0918a
chore(vscode): update development guide ( #1121 )
2023-10-31 07:32:15 +00:00
Boshen
eaa0c58e24
feat(linter): eslint-plugin-unicorn(filename-case) ( #978 )
2023-10-11 15:23:17 +08:00
Boshen
817f8c295e
ci: turn off doc tests because they are slow to compile and run ( #961 )
2023-10-07 17:01:23 +08:00
阿良仔
7763197da3
fix(vscode): avoid unwrap when oxc plugin file doesn't exist ( #817 )
2023-08-30 21:30:22 +08:00
u9g
a38619b780
feat(vscode): Add linter plugin to vscode extension ( #813 )
2023-08-29 23:35:32 -04:00
Boshen
5152b39b17
chore: clean up Cargo.toml with cargo machete ( #767 )
2023-08-20 15:29:09 +08:00
Boshen
6f1daa67b2
refactor(cli): clean up lint and cli options ( #759 )
2023-08-19 00:06:12 +08:00
Boshen
2f48bdf26f
fix(parser,semantic): make semantic own Trivias ( #711 )
...
closes #708
Making the parser return Rc<Trivias> is not a good API, and ideally
`Semantic` should just own `Trivias` so it can process or mutate it.
2023-08-10 15:30:32 +08:00
阿良仔
8a915cec5c
feat: vscode extension ( #690 )
...
related: #688 .
There are some unfinished things that need to be finalised by Boshen.
1. Official icon and description for the package.
2. Publishing strategy ( It's probably not a good idea to use
`package.json` as a probe to publish extension, as there's too much
vscode configuration coupled to it, a git tag like `vscode_v0.0.x` might
be worth considering ).
3. License for the extension.
2023-08-06 21:28:49 +08:00
