-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[prettierx] provide the additional formatting options in a prettier plugin #8
Comments
with the additional formatting options as discussed in brody4hire/prettierx#37
- Add note that it is desired to provide the additional formatting options in a prettier plugin as discussed in brody4hire/prettierx#37 - Add phrase that brody4hire/prettierx#40 is resolved by brody4hire/prettierx#41 which is to be included by an upcoming merge.
I think the ultimate design would be a pipeline-based toolset which uses the Acorn parser data structure, which seems to be how Babel JS works. I really like the general design of remark (https://remark.js.org/), which does Markdown processing in a set of plugins and is based on unifiedjs (https://unified.js.org/). A step further may be to use a Flow Based Programming paradigm, like they did in |
I made a couple of Prettier plugins that can use this formatter, with the new formatting options in this package from a configuration file:
Next step: support using Babel parser with TypeScript, as proposed in prettier/prettier#6400 I suggested in idea in prettier/prettier#6888 to support use of the standard (Microsoft) TypeScript implementation by moving it out to a plugin, rather than bundling it with Prettier itself. (As I said in #48, I do not bundle TypeScript parser with this package anymore.) Next step would be to demonstrate using Babel TypeScript parser from a plugin. |
New Prettier plugin working with both Babel & TypeScript: https://github.com/brodybits/prettier-plugin-x This project shows eslint, Prettier, Documentation needs to be updated. |
* Language parsers are supported as if this were `prettier` version `1.15.3` / `1.16.0`; * old language parsers are deprecated as if this were `prettier` version `1.15.3` / `1.16.0`.
(fix lint issue introduced in PR #8)
as documented in https://prettier.io/docs/en/plugins.html#printers
This idea should make it easier to integrate with existing eslint plugins and other existing tools.
P.S. An interesting question on this subject asked in prettier/prettier#5747.
The text was updated successfully, but these errors were encountered: