-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
A missing prettier
formatter is silently ignored
#111
Comments
Ok, seems like the problem simply was that prettier was not installed. Manually installing it and rerunning Would it be possible to either:
Same for Biome, I guess. |
prettier
formatter is silently ignored
This you for opening an issue. This library passes the values provided to @hey-api/openapi-ts to run the formatting. It would/could become a maintenance burden to add the checks in this library, opening a ticket in @hey-api/openapi-ts package may be helpful. I personal do not believe a cli command should install a package automatically. A console warning would be good. |
I am starting to believe we should remove the options for consumers to interface with the format and linter options as this library's generated code will be covered. And change in the underlying service generators formatted would have to maintained in this libraries. Feels hard to maintain. Would be consistent for the consumer to run their own linter and formatted after generating the files. |
I completely agree with you. |
For the record, I agree as well, and we have already switched from using the |
So, given that I believe no work is planned to address this as instead the |
Describe the bug
Generated files under "requests" have tabs instead of spaces although
prettier
is configured otherwise.To Reproduce
I have a
.prettierrc
withand run
openapi-rq -i http://localhost:8080/swagger-ui/api.json -o src/api --format prettier
.The generated *.ts files have tabs instead of spaces.
OpenAPI spec file
n/a
Expected behavior
Spaces instead of tabs should be used according to the
prettier
configuration.Additional context
The text was updated successfully, but these errors were encountered: