[FEATURE]: Implement Config File about sqruff HOT 4 CLOSED

@benfdking & @gvozdvmozgu to review

from sqruff.

A few of my thoughts/opinions that are running through my mind

I would start by not deviating from anything that sqlfluff does. In my mind, our V1 should still try to be as close as possible in terms of fidelity. Even if that is sub-ideal long-term, it just makes it easier to test/debug/develop when we have a clear comparison point.

For V2 and having achieved some parity, I think it's important that the rule options become more strict in code. The options at the moment are in maps and I think letting each rule define its parameters, as well as any rule cross dependencies and what it can take, will make the project much easier to debug at scale.

For example, at the moment, we have a default config that is a [toml] file. I think we should be able to generate a file from each rule that gives it its "default."

I think we should then try to move away as much as possible from maps into strict types that make the project feel more robust and probably also more performant. Once those things are in place, I think it will then be much easier to move defaults and then try to part ways with sqlfluff.

from sqruff.

It seems this is already implemented? At least version 1, as described above

from sqruff.

👍

Happy to close. @louisjoecodes ?

from sqruff.