Andy Hall (fenomas)

@Divlo > If you really want this behavior, you could open an issue in the ESLint repo. As far as I know eslint's formatter is safe by default. The rule...

> A linter looks at the piece of code as is. It doesn't assume that any code has been commented out or should be expected to be added. I fully...

@dougwilson Of course I'm aware that `unused-vars` isn't fixable in eslint - I was just making an illustrative comparison for why the `prefer-const` rule shouldn't be applied by default. >...

@dougwilson > **What did you expect to happen?** > A warning about let variables that are not reassigned would be the right approach, without auto-converting them. But if that's not...

Thanks for clarifying that @dougwilson. In that case, per my last comment I think the right thing to do here is for standard to not enable `prefer-const` by default. PS:...

I only ask because (a) the policy appears to not exist, and (b) it's the only reason given so far for why this issue is closed. Honestly, I'm not trying...

@dougwilson Understood, and thanks for clarifying. (questions for maintainers about the "only final code" policy remain open.)

> The decision to make prefer-const fixable lies with ESLint > Hence making this an issue with ESLint, not standard. @voxpelli I'm not suggesting that `prefer-const` should not be fixable....

Thank you for the links - I searched issues, but I didn't think to search pull requests.

I've just realized, maybe the disconnect here is whether `standard --fix` is an **autoformat** command, or whether it's a **fix conformance errors** command. The readme and other docs here describe...