-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Expose list of supported parsers, etc. #3023
Copy link
Copy link
Closed
Labels
locked-due-to-inactivityPlease open a new issue and fill out the template instead of commenting.Please open a new issue and fill out the template instead of commenting.status:has prIssues with an accompanying pull request. These issues will probably be fixed soon!Issues with an accompanying pull request. These issues will probably be fixed soon!status:needs discussionIssues needing discussion and a decision to be made before action can be takenIssues needing discussion and a decision to be made before action can be takentype:editor supportIssues about tools Prettier provides for use inside editor integrations.Issues about tools Prettier provides for use inside editor integrations.
Metadata
Metadata
Assignees
Labels
locked-due-to-inactivityPlease open a new issue and fill out the template instead of commenting.Please open a new issue and fill out the template instead of commenting.status:has prIssues with an accompanying pull request. These issues will probably be fixed soon!Issues with an accompanying pull request. These issues will probably be fixed soon!status:needs discussionIssues needing discussion and a decision to be made before action can be takenIssues needing discussion and a decision to be made before action can be takentype:editor supportIssues about tools Prettier provides for use inside editor integrations.Issues about tools Prettier provides for use inside editor integrations.
Currently every time Prettier adds another language, a lot of editor integrations have to release another version of their plugin to support it. This might be adding more language types, extensions, etc.
I'm wondering if we'd be able to support some kind of feature detection within Prettier that editor integrations can call and run more dynamically. Something along the lines of:
Which might return:
Would be nice to release this alongside Markdown support.
Love to get some feedback from some plugin maintainers on whether this kind of thing could be useful.
cc. @robwise @CiGit @mitermayer