Skip to content

Commit

Permalink
Mention RFC in /arewepluginsyet (#15)
Browse files Browse the repository at this point in the history
* Update arewepluginsyet.ts

Updates the description for `/arewepluginsyet` with a mention of the latest RFC and a summary.

* Apply suggestions from code review

---------

Co-authored-by: Superchupu <[email protected]>
  • Loading branch information
arendjr and SuperchupuDev committed Feb 7, 2024
1 parent 2a89786 commit 47b536f
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions src/commands/arewepluginsyet.ts
Original file line number Diff line number Diff line change
Expand Up @@ -9,17 +9,17 @@ export async function onPluginsSlashCommand(interaction: APIApplicationCommandIn
⚠️ **In roadmap**
There is no support for plugins yet, but it is planned for the future.
From the [2024 roadmap](https://biomejs.dev/blog/roadmap-2024/):
>>> ### Plugins
We will explore plugins and come up with a design that fits Biome. Biome is different from other tools because Biome is a toolchain that has multiple tools in it, so we have to think out of the box and propose a design that might differ from the tools people are used to.
There is a [Biome Plugins Proposal RFC](<https://github.com/biomejs/biome/discussions/1762>) that aims to guide our implementation work.
We don't know yet what a Biome's plugin will look like, although a plugin should be able to tap all the tools that Biome offers.
We want to support the following use cases:
Some ideas that we will consider:
- Linter plugins
- Formatter plugins
- Transformation plugins
- Codemods
- A query engine
- DSL
- WASM
- A Runtime
Specifically, we want to explore these use cases through a combination of [GritQL](<https://docs.grit.io/tutorials/gritql>) plugins and/or JS/TS plugins.
`,
});
}
Expand Down

0 comments on commit 47b536f

Please sign in to comment.