Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
closes #65
Mostly a stripped down copy of the trigger member implementation for
anonymousUnit. Does not impose any of the anonymous restrictions like disallowingstatic. Simply allows you to parse things like classes, methods and statements in the same file/block of text as you would find in a.apexscript file.Previously the
checksystem tests only read sfdx-project directories, which avoided various invalid .cls template files that contain tokens like%variable%. Unfortunately this also means it won't pick up any.apexscript files since they are outside projects. So it now runs an additional check using a list of certain samples that are known to have script files.Manual test running
checkon samples had many broken .cls files, but no errors on .apex files: