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

The enabled/disabled check is now applied after expression parsing #839

Merged
merged 2 commits into from
May 12, 2021

Conversation

qw3ry
Copy link
Contributor

@qw3ry qw3ry commented May 11, 2021

This means, that 'enabled' and 'disabled' can be used as part of a permission expression.
For example: 'a+enabled,!disabled+b' works now as expected and is equivalent to 'a,b'

Tobias Beeh added 2 commits May 11, 2021 16:02
…on parsing

This means, that 'enabled' and 'disabled' can be used as part of a permission expression.
For example: 'a+enabled,!disabled+b' works now as expected and is equivalent to 'a,b'
@qw3ry qw3ry merged commit 529db70 into develop May 12, 2021
@qw3ry qw3ry deleted the tbe/se-10600-allow-nested-enabled-permission branch May 12, 2021 10:28
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.

None yet

7 participants