-
Notifications
You must be signed in to change notification settings - Fork 101
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
Add Prettier linting to project #253
Comments
Can I tackle this issue? |
I left an important comment considering the Prettier implementation here |
@h1divp any update on this? Should we close? |
Idk the person currently assigned hasn't responded to my last message, or otherwise I haven't heard from them |
I wouldn't close it but rather reassign if no progress is made soon |
Can I be added to this issue? |
Hey, could I get clarification on what we are aiming for? Do we want to support prettier on any IDE or just VS Code? I ask because I have an idea of how to implement it if we were to just support VS Code but if we want to support more I can look into it. Edit: I mean as far as formatting on save |
Linting (which automatically formats saved files to have correct whitespacing, semicolons at the end of line, etc) is currently implemented in our Github actions pipline (automated testing system) but I think it would be beneficial to add Prettier support so that the linter runs after people save files in their IDE or text editor. Prettier is quite popular, and I also think we should recommend it in the documentation. That being said, even if we do add support, using prettier should still be completely optional, and just for those who would like to use it.
Note that this will need to be set up separately for both the front-end and back-end.
The text was updated successfully, but these errors were encountered: