Why in the world would you want to develop something that doesn't follow the coding rules required by your org, just so you can go back and fix everything before submitting a PR? That's just extra work.

[–] [email protected] 4 points 1 year ago (1 children)

Because you want to know if the first half of the code works at all before you write the whole second half.

Finding all the bits that will be used by the second half and changing the declarations to just expressions is a bunch of extra work. As is adding placeholder code to use the declared variables.

[–] [email protected] 1 points 1 year ago (1 children)

I'm having a hard time envisioning a situation where testing my code requires a bunch of unused variables. Just don't declare the variables until you've started writing the code that uses them...

[–] [email protected] 3 points 1 year ago (1 children)

Most of the time you don't write the code, you change it.

I had tons of situations where I wanted to test deleting a code block which just happened to use an imported library, which the compiler is now complaining about because it's no longer being used.

[–] [email protected] 1 points 1 year ago

If that’s the problem, then I would just use something like goimports to auto fix the imports every time I hit save. I never even see those errors so they don’t bother me.