Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is just for code consideration. I have been using sqlfluff as a linter and am finding sometimes sqlfluff will lint the compiled code instead of the source code. The
one_hot_encoder
compiled code is littered with whitespaces that might throw errors if sqlfluff were to lint it. Such as the trailing whitespaces aftercase
andthen 1
in the macro I've partially edited. These whitespace issues as well as the amount of useless new lines created. I wanted to get the owners' thoughts on this cleanup and if this type of cleanup is worth the effort.Example CTE before edits:
Example CTE after edits: