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: Multiple sections type #320

Closed
wants to merge 1 commit into from
Closed

Conversation

Gabriel-403
Copy link
Contributor

If you need multiple policy definitions or multiple matcher, you can use like p2, m2. In fact, all of the above four sections can use multiple types and the syntax is r+number, such as r2, e2. By default these four sections should correspond one to one. Such as your r2 will only use matcher m2 to match policies p2.

You can pass in EnforceContext as the first parameter of enforce method to specify the types, the EnforceContext

fix: #311

@Gabriel-403 Gabriel-403 changed the title Fix: Multiple sections type fix: Multiple sections type Aug 21, 2021
@Zxilly
Copy link
Contributor

Zxilly commented Aug 21, 2021

plz don't mess unit tests, use semantic commit style and rebase the git history but not merge

Signed-off-by: Gabriel-403 <[email protected]>
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@nodece
Copy link
Member

nodece commented Mar 2, 2022

This feature has been released at the NPM beta channel.

@nodece nodece closed this Mar 2, 2022
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.

Multiple policies config?
4 participants