Closed tchoutri closed 1 year ago
That option hasn't been released yet. But the released version includes the Ormolu change that always enables it
@brandonchinn178 ah, hence my confusion! Because I was reading the README for main
and I didn't realise the tuning option for Fourmolu had been released after the integration of the Ormolu option.
Not sure if I'm going to be the only one bitten by it, but the update by Dependabot of my CI checks was definitely surprising when I realised I couldn't turn it off. :)
For sure. The Fourmolu Live PR moves the docs for the config options to a website that will say what version each config option was added in (including unreleased options), so this confusion will hopefully be prevented in the future.
Yesterday I was updating our codebase to 0.11 and this bit me as well. Would it make sense to have a CLI flag that would spit out "default config" (maybe with commented out variants for each flag) to stdout?
@jhrcek Sure! Or maybe (following ghc
's lead) fourmolu --info
printing out the resolved config (defaults + config file)? Feel free to open a separate issue!
I've disabled the
single-constraint-parens
option in my fourmolu.yaml file and yet it appears not to be taken into account:Am I missing something obvious?