Closed m-tyler closed 1 year ago
You mean text after /copy
or /include
are being checked against for casing?
The topic was about code within my program like this.
This is a production copy of the copy book
But looking at the /copy lines I see it there also.
This is only an ask for consideration if this is a good idea. I think it is because it can allow me to move to a non-all upper case code from the olden days to easier on the eyes lower/mixed case code at a slower pace where I also need some justification for modifications at times.
Well, this is a curious topic. In theory, it's working as expected. You've open a member which has an applicable rpglint
member in the same library, but can includes files from other libraries which doesn't have an rpglint
setup. Got to think a lot about this one.
The obvious bug here is the 'variable name casing' error appearing on /copy
and /include
directives. I am going to fix that ASAP
Anything would be great.
Released with 0.21.4.
With version 0.21.3, the ability for the tool to find source on the library list work superb however, it now has shown me something that I cannot do anything about most of the time.
My production copy books are being flagged for wrong case items in my development source. I don't have the option to always check out that source and modify it and I don't want return the variable case pattern I use to match production copy. I could sprinkle a ton of
// @rpglint-skip
before each line don't want to adjust but there are cases when the code has a lot of references to production code that is not the same case as the current development copy.Its not that I don't want the code to be consistent but I don't always have the time or necessary authorization to modify source just to alter the source case style.
So I ask to have this considered for the linter, an option that I set to tell it that I only want the rules to apply source that also has a linter member.
Thanks, Matt