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(replaceeval): add third param to replaceEval and only replace eval() w/ matching ruleName #316

Merged
merged 1 commit into from
Aug 17, 2021

Conversation

JoshuaCWebDeveloper
Copy link
Contributor

This fixes #315.

I chose to go with a slightly more straightforward approach than what was done in casbin/casbin#620; however, this meant modifying an existing util function instead of creating a new one.

@JoshuaCWebDeveloper
Copy link
Contributor Author

I tried following the instructions in the DCO details with the same result, not sure what the issue is.

@hsluoyz
Copy link
Member

hsluoyz commented Aug 16, 2021

@Zxilly @Gabriel-403 plz reivew

Copy link
Contributor

@Zxilly Zxilly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, but this may break lagacy array definition grammar, I will later submit a patch

@Zxilly Zxilly merged commit bd4f5bf into casbin:master Aug 17, 2021
github-actions bot pushed a commit that referenced this pull request Aug 17, 2021
## [5.11.4](v5.11.3...v5.11.4) (2021-08-17)

### Bug Fixes

* **replaceeval:** add third param to replaceEval and only replace eval() w/ matching ruleName ([#316](#316)) ([bd4f5bf](bd4f5bf)), closes [#315](#315) [#315](#315)
@github-actions
Copy link

🎉 This PR is included in version 5.11.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@JoshuaCWebDeveloper
Copy link
Contributor Author

lgtm, but this may break lagacy array definition grammar, I will later submit a patch

😬 Let me know if you want help with that. (And thanks!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] A matcher with multiple eval() doesn't work
3 participants