-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
Multiple Request Types with Eval #354
Comments
Thanks for your feedback and for bringing this to our attention. I've done some digging into the issue you've reported. Upon investigation, I've found that issue #108 has addressed the use of different Request Value types, and the ABAC eval model can now operate without errors. Regarding the use case you mentioned, I've come up with a potential solution that could work. I propose modifying the system to ignore parsing exceptions only under the ABAC eval model and assume that the result of the matcher is false. This approach seems promising and I believe it's worth trying out. I'll be looking into implementing this solution and will keep you updated on my progress. |
Thanks! Any ETA on when you'll know if the proposed solution will work and if it can be merged into the main branch? |
This question seems similar to #108, but that seemed to be resolved, but I am not able to get my test working.
I am trying to use a single model that uses eval with different request models.
Using Casbin.NET v2.7.
model.conf
policy.csv
Program.cs
When executing I receive,
DynamicExpresso.Exceptions.ParseException: No property or field 'Property1' exists in type
.Is it possible to have multiple request models and a single policy?
edit: I should say that this same behavior occurs if using anonymous types or not.
The text was updated successfully, but these errors were encountered: