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

Adds theClass(..), noClass(..), should().be(..) and should().notBe(..) #80

Merged
merged 4 commits into from
Jun 19, 2018

Conversation

msherman32
Copy link
Collaborator

Extended the syntax to offer an ArchRuleDefinition.theClass(..) and noClass(..) entry point to create rules based on a specific class. Also added should().be(..) and should().notBe().

Issue: #60
Signed-off-by: Michael Sherman msherman32@gatech.edu

Michael Sherman and others added 4 commits June 19, 2018 19:30
noClass(..) entry point to create rules based on a specific class. Also
added should().be(..) and should().notBe().

Issue: TNG#60
Signed-off-by: Michael Sherman <msherman32@gatech.edu>
…l with the new (not)be(..) methods)

Issue: TNG#60
Signed-off-by: Peter Gafert <peter.gafert@tngtech.com>
…uld().be(..) and should().notBe(..)

Issue: TNG#60
Signed-off-by: Peter Gafert <peter.gafert@tngtech.com>
@codecholeric
Copy link
Collaborator

Thanks a lot!! 😄
I've added some minor fixes (@PublicAPI missing) and some examples / integration tests for the new syntax.

@codecholeric codecholeric merged commit a76d0c9 into TNG:master Jun 19, 2018
@codecholeric codecholeric added this to the 0.9.0 milestone Aug 19, 2018
codecholeric added a commit that referenced this pull request Feb 21, 2021
Adds theClass(..), noClass(..), should().be(..) and should().notBe(..)

Resolves: #60
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.

2 participants