Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Separate rules into individual files
See original GitHub issueI’ve hit an issue with my contribution on https://github.com/sqlfluff/sqlfluff/pull/577 (L035) where git was mixing up my issue with a newer issue (L036) when rebasing my branch.
Another issue that came up is that another rule https://github.com/sqlfluff/sqlfluff/pull/678 was started with the identifier L035 which is technically free since my PR was not merged yet. One of those contributions will have to be changed to L037 and then the actual code needs to be ordered in the file properly so L035 comes before L036 and then L037
I think we should just break-up the std.py file into one file per rule just like we did for tests to avoid these issues.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I agree –
std.pyhas become way too large: about 3,500 lines and counting. I’m happy to rename “my” L035 if needed.That approach should work fine. The important thing about auto discovery is that it probably sounds more complex than it is.