-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Relax pragma rules #48
Comments
Seems reasonable to me. |
I actually just got pragma functionality merged into prettier itself: prettier/prettier#2772. Right now it requires the docblock format (so no I filed a separate issue here to discuss this plugin's migration to the new core option at #54 |
Closed as pragma functionality has been removed in favour of using prettier's native pragma support as of v3 |
At the moment the pragma has to be the first line and in the
/** @yourPragma */
format. If it's used in a file with Flow it means you have to remember to put the Prettier one first.This isn't a huge hassle but it caused me a few minutes of confusion as I thought I had things set up wrong. It would be nice if this plugin's pragma were more like Flow's and could be in either
// @yourPragma
or/** @yourPragma */
format and be anywhere in the file.The text was updated successfully, but these errors were encountered: