Protected files really necessary? #1919
Closed
martinbiard
started this conversation in
General
Replies: 1 comment
-
I opened a PR: #1920 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Current list of protected files:
I was a little disappointed that I could not rely on biome to ensure consistency across my tsconfig files. I initially thought it was a bug and wasted some time debugging why my tsconfig.json was being ignored until I found the above page listing protected files. I think it's understandable that files meant for machines (package-lock.json, yarn.lock, etc.) are left untouched but why avoid processing files written by developers? Right now, if I want to format a tsconfig.json file, I first need to rename it to tsconfig.tmp.json, format it, and rename it back. I think this list should be configurable and left to the developer to decide which file(s) to process or not. Typically, with other tools, you would have such files part of ignore directive by default, but always reconfigurable by the developer.
Beta Was this translation helpful? Give feedback.
All reactions