IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

Update docs/enforce-style-conventions-with-fmt.md

Browse Source 
Co-authored-by: tom-reinders <tom-reinders@users.noreply.github.com>
Signed-off-by: esprimo <johan.edholm90@gmail.com>
This commit is contained in:
esprimo 2024-03-25 16:02:14 +01:00 committed by GitHub
parent 4b4f16f253
commit 72d8890514
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/enforce-style-conventions-with-fmt.md
View File

@ -248,5 +248,5 @@ This convention says they _can_ be grouped, rather than _should_ or _must_ be gr
Other things to consider:
- Do we want any or all of the conventions to be optional/configurable?
- I suggest we add as few options as possible, but having an option to out in our out of the new behavior could probably be good (e.g. `tofu fmt --legacy` or `tofu fmt --strict`) to allow backwards compatibility.
- I suggest we add as few options as possible, but having an option to opt in or out of the new behavior could probably be good (e.g. `tofu fmt --legacy` or `tofu fmt --strict`) to allow backwards compatibility.
- We also have the option of releasing one or two conventions at a time/iteratively rather than a big bang release with all conventions right off the bat.