Git Product home page Git Product logo

Comments (4)

simonhaenisch avatar simonhaenisch commented on May 22, 2024

Hey I think what you could do is set a plugin list manually (i think you can also configure them via plugins option in .prettierrc/equivalent), which then disables the auto-loading of this plugin. Then you import the parsers from this plugin and wrap them in your own custom plugin.

const { parsers: organizeImportsParsers } = require('prettier-plugin-organize-imports');

const myCustomParser = (code, options) => {
 // do the things

  return customizedCode;
}

exports.parsers = {
  typescript: (code, options) => myCustomParser((organizeImportsParsers.typescript(code, options)), options),
  // ... equivalent for babel parser
};

Let me know if that works, would be good to know (:

from prettier-plugin-organize-imports.

wdfinch avatar wdfinch commented on May 22, 2024

Hey thanks for the advice. The only problem is my plugin is open source and therefore I can't assume that people will be using your plugin and mine together. Is there any solution like this that would work generically without making that assumption other than just checking for every possible plugin that could conflict?

Additionally is there some solution like this that could be implemented outside the plugin via the prettier CLI or config?

So far the best I've found is to just run prettier again choosing your plugins manually in cases where you have conflicts. It'd be nice if I could run it all the plugins in one go.

from prettier-plugin-organize-imports.

simonhaenisch avatar simonhaenisch commented on May 22, 2024

Ok I think I misunderstood you, I thought you were talking about a project-specific custom plugin, not another publicly available one. Yeah for that problem I don't think there's a solution really other than what you already said about double-running prettier with different plugin lists, or people manually chaining the plugins like above, via a custom plugin in their project.

Since the Prettier team doesn't consider this plugin a valid use case for the plugin API, I don't have much hope that anything will change that makes plugins like this more compatible.

from prettier-plugin-organize-imports.

wdfinch avatar wdfinch commented on May 22, 2024

Makes sense. Thanks for the advice.

from prettier-plugin-organize-imports.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.