[bug] the commit "fix: not use ref values to transform" failed the CI tests about casbin-aspnetcore HOT 6 CLOSED

@sagilio @sociometry @AsakusaRinne

from casbin-aspnetcore.

Ok. I will fix it later. This commit will fix another BUG, we can not reset it.

from casbin-aspnetcore.

@sagilio why did you remove my fix for: #58 (comment) ? The fix commit: d0fa72b is not in any branch now

from casbin-aspnetcore.

@sagilio why did you remove my fix for: #58 (comment) ? The fix commit: d0fa72b is not in any branch now

@hsluoyz

p, [email protected], BasicTest, Get

This policy is an example of the basic transformer, it is not wrong here.
it needs the user to change the default transformer options to test it. I commented on the reason here (#58 (comment)).

In fact, I have tried to enhance the experience for the user trying the example by setting the transformer at the attribute. But the change is in the reverted commit and there is a little logic conflict with your commit

So I recovered the backup branch and only cherry-pick the last commit to make sure the last version worked well.

from casbin-aspnetcore.

it needs the user to change the default transformer options to test it. I commented on the reason here (#58 (comment)).

I don't think it makes sense if it has made a lot of people think it's a bug. It's not a good example code. If you want to show some special transformer functionality, then you create a "working" example especially for it. The example itself SHOULD be working out-of-box. Above all, the result we see is that the user experience has been impacted by the wrongly-designed example, long-time no response in the issue, and broken CI for several months. I don't think this is a good way to maintain the software responsibly.

from casbin-aspnetcore.

it needs the user to change the default transformer options to test it. I commented on the reason here (#58 (comment)).

I don't think it makes sense if it has made a lot of people think it's a bug. It's not a good example code. If you want to show some special transformer functionality, then you create a "working" example especially for it. The example itself SHOULD be working out-of-box. Above all, the result we see is that the user experience has been impacted by the wrongly-designed example, long-time no response in the issue, and broken CI for several months. I don't think this is a good way to maintain the software responsibly.

You are right, the example code needs to enhance and I'm also sorry for the lack of time to positively maintain it lately, I will improve it.

from casbin-aspnetcore.