Updated Readme with Linter Options for Encapsulation Checks (OaM)#123
Open
WolframPfeifer wants to merge 3 commits intoopprop:masterfrom
Open
Updated Readme with Linter Options for Encapsulation Checks (OaM)#123WolframPfeifer wants to merge 3 commits intoopprop:masterfrom
WolframPfeifer wants to merge 3 commits intoopprop:masterfrom
Conversation
Co-authored-by: Werner Dietl <wdietl@gmail.com>
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
1 participant
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.
In this small PR, I added a section in the Readme about the OaM (Owner as Modifier) linter option, since it was not documented so far.
I noticed that in the code there are more supported options. However, two of them (
warn,allowLost) are declared in the code but seem to be unused, and the third one (checkStrictPurity) just checks that the code does not contain any assignments at all. So I don't think it is very useful to document these, but if desired I can add it ...This PR should be merged after #120.