Skip to content
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

Fix linter behavior for RPGLEINC files #340

Merged
merged 3 commits into from
Nov 10, 2024

Conversation

worksofliam
Copy link
Contributor

The linter now correctly ignores specified rules when processing RPGLEINC files, addressing the issue where it was incorrectly firing on these include files. A test case has been added to verify this behavior. Unused log statements have also been removed for cleaner code.

Fixes #338

@worksofliam worksofliam merged commit 0ed394f into main Nov 10, 2024
2 checks passed
@Gregory1701
Copy link

Thanks @worksofliam ! But, I'm not on v0.26.13 and it's still firing on my source which is RPGLEINC. Did I misunderstand and this isn't out yet?

@worksofliam
Copy link
Contributor Author

@Gregory1701 are you working in a source member, stream file or local?

@Gregory1701
Copy link

old fashioned source member, my friend. It's in QCPYSRC.

@worksofliam
Copy link
Contributor Author

worksofliam commented Nov 11, 2024

@Gregory1701 what is the attribute/extension of the member?

@Gregory1701
Copy link

Gregory1701 commented Nov 11, 2024

@worksofliam
image

@worksofliam
Copy link
Contributor Author

@Gregory1701 Additional fix, 0.26.14, is out now, which solves this issue. I forgot member attributes in VS Code as not very simple.

@Gregory1701
Copy link

Thanks @worksofliam , it's better, but still throwing one error. Is that intentional?
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RPG Linter firing even on copy books
2 participants