You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest code formatters are getting better at formatting code in a reliable and consistent manner. Some implications in case we adopt this for GRNsight:
We will want to configure the code formatter in a manner that use a style that the team agrees upon
There will be a “formatting-only” transition phase where the code formatter may need to make a wide array of edits in order to sync up the code to the latest style
Set up repo so that independently of the code editor being used. Might need to reckon with 4 spaces of indenting vs new standard for javascript which is 2 spaces of indenting. Could be implemented in the GitHub Actions workflow.
kdahlquist
changed the title
Consider adopting a late-generation code formatter for GRNsight
Integrade code formatting specifications into the GRNsight repo
Feb 6, 2025
Prettier has established itself as the de facto code-formatter for many repos, so we will just go with that. We will need a .prettierrc file (or similar mechanism) on the repo, and make sure that our editors are configured to use it
If we change format, step (2) in the original description may still need to take place
The latest code formatters are getting better at formatting code in a reliable and consistent manner. Some implications in case we adopt this for GRNsight:
Formatter for consideration: https://prettier.io
The text was updated successfully, but these errors were encountered: