From 72d8890514276b6ebd5b01f27bf5d90550e11c5a Mon Sep 17 00:00:00 2001 From: esprimo Date: Mon, 25 Mar 2024 16:02:14 +0100 Subject: [PATCH] Update docs/enforce-style-conventions-with-fmt.md Co-authored-by: tom-reinders Signed-off-by: esprimo --- docs/enforce-style-conventions-with-fmt.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/enforce-style-conventions-with-fmt.md b/docs/enforce-style-conventions-with-fmt.md index ef26ff0e2f..92ea4a1811 100644 --- a/docs/enforce-style-conventions-with-fmt.md +++ b/docs/enforce-style-conventions-with-fmt.md @@ -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. \ No newline at end of file