Open willparsons opened 1 month ago
Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:
Proper conventional commit scoping:
If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin
If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error
[ ] Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above
[ ] README
is properly formatted and uses fenced in links with <url>
unless they are inside a [title](url)
[ ] Proper usage of opts
table rather than setting things up with the config
function.
just found this for picking the formatter dynamically: https://github.com/LazyVim/LazyVim/issues/2116#issuecomment-1971805431
will look into it
I think at this point it should just be typescript-biome and not like this.
I.e pack/typescript-biome
updated the structure 👍🏻
Closes #962
TODO
📑 Description
biome
pack:pack.typescript-biome
.pack.typescript.core
.ℹ Additional Information
I pulled out the
core
of the typescript pack so that the eslint+prettier and biome configuration can be separated easily. The default forpack.typescript
hasn't changed.