-
Notifications
You must be signed in to change notification settings - Fork 941
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup Logic for loops #739
Conversation
I hate to be a buzz killer .... but aren't we reaching the limits of BASH scripts ? |
@nvuillam I think I agree... It may be an interesting idea to get some help for I had always hoped we would get some component action steps and be able to split this up to be more reasonable, but that point has not been reached yet :) |
@admiralAwkbar > I never learned to code in Python... maybe it could be an occasion to spend a week-end doing that, I'll think about it ... 😄 For my "high level" point of view, we could keep all repo content except the /lib folder who would need to be rewritten, do you confirm ? |
@admiralAwkbar I was too tempted to resist .... :D |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This approach looks good to me
I dont think i like this approach anymore and need to look at this more |
So this is a crazy idea on how we get into the basic loops...
But the main idea is that we create 2 sets of data:
We then use that data to see if we need to even go into the specific linter loops.
This would help stop going into loops where the user has no code. Hopefully eliminating many random failures for languages users are not using.
Its a fun idea, and might take some more cleanup