Closed thoraj closed 2 years ago
@sagilio @xcaptain @huazhikui
@sagilio
I have forked the project and "fixed" the bug i master. I have verified the fix by setting up a pipeline to build a nuget, and consumed the forked nuget in our solution.
I would strongly prefer to not have a private fork of Casbin in production, and would like to know how to get the fix into the released Casbin.Net package?
If this is not possible, could you say which branch/tag we should use in our private package? The idea is to have something as close to the released Casbin as possible.
@thoraj why not make a PR? Contributions are welcome!
:tada: This issue has been resolved in version 1.12.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 1.12.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
I have a need to use a custom key-matcher for my g grouping policy:
I noticed there is a way to set matching func for domain as shown in the test:
But cannot make this work as it seems to operate on the x.sub values and not x.dom values?
When digging into the source, it seems to not set the function properly? And I think maybe this is a bug (?).
https://github.com/casbin/Casbin.NET/blob/a5122e846ce02463ad84bc4ff966b9efe343406c/NetCasbin/Extensions/EnforcerExtension.cs#L28
Shouldn't this code call
AddDomainMatchingFunc()
instead of theAddMatchingFunc()
?