Replies: 7 comments 91 replies
-
Use case: FormatterDo you think Biome's formatter should support plugins? If so, what kind of things you want to use it for? Please keep in mind we cannot format anything we cannot parse. Does that mean our parser should support plugins too? Speak your mind! |
Beta Was this translation helpful? Give feedback.
-
Use case: LinterDo you think Biome's linter should support plugins? If so, do you have specific rules in mind? What kind of API do you think we could use to report diagnostics? How would we support fixers? Let us know! |
Beta Was this translation helpful? Give feedback.
-
Use case: TransformerDo you think Biome's upcoming transformer functionality (see roadmap) should support plugins? Or maybe it should even be built around plugins from the ground up? Your ideas are appreciated! |
Beta Was this translation helpful? Give feedback.
-
Use case: Query engineLinter and Formatter are too task-specific. What underlies each of them is querying, and querying is a desirable ability even in the absence of the need to change formatting or detect known mistakes. If Biome is the thing tasked with understanding conceptual overlays on your code, I would definitely hope that I respond to queries without requiring me to define a lint rule or a formatter plugin. |
Beta Was this translation helpful? Give feedback.
-
Use case: Codemodhttps://github.com/facebookarchive/codemod Codemods can be used to help migrate codebases or adopt new patterns. |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
Use Case: Tailwind Class SortingPrettier just had an update that handles tailwind class sorting, which would be a nice addition to biomejs. https://tailwindcss.com/blog/automatic-class-sorting-with-prettier |
Beta Was this translation helpful? Give feedback.
-
Update: A follow-up RFC, based on the results and discussions here, has been presented: #1762
As many of you are aware, Biome's roadmap for 2024 includes the goal to develop a plugin system. But as the post mentioned, we don't yet know what those plugins will look like, what use cases they will cover and/or what technology we will use to implement them. What we do know, is there are plenty of ideas out there :)
So rather than proposing a specific solution, this RFC is intended to gather your input: What functionality do you miss in Biome, and do you think a plugin might help to cover it? What are you looking forward to in plugins the most? What will make or break our plugin system in your mind? This is the place to speak up!
I have attached a poll to take people's votes on preferred technology choices, and I will also create a few threads to help guide the discussion around various use cases. If you think anything is missing, feel free to create your own! You can also upvote use cases you think should be prioritized.
359 votes ·
Beta Was this translation helpful? Give feedback.
All reactions