But if I understand all correct, now a default provider not use filters. As I saw in source code a default behaviour for adapters are to load all policies on initialization. But not for optimization the EF core adapter has a lazy loading (when we load zero policies on initialization). Will I need to implement a custom provider for this variant if I want to load policies with a filter before call enforce?
Hi. I saw some questions: https://github.com/casbin-net/casbin-aspnetcore/issues/17 , https://github.com/casbin-net/casbin-aspnetcore/issues/34 , https://github.com/casbin-net/casbin-aspnetcore/issues/36 , https://github.com/casbin-net/casbin-aspnetcore/issues/37 , https://github.com/casbin-net/casbin-aspnetcore/issues/41 . Also I saw example https://github.com/casbin-net/casbin-aspnetcore/tree/preview/samples/WebApplicationWithEfcoreSample (thank you for it).
But if I understand all correct, now a default provider not use filters. As I saw in source code a default behaviour for adapters are to load all policies on initialization. But not for optimization the EF core adapter has a lazy loading (when we load zero policies on initialization). Will I need to implement a custom provider for this variant if I want to load policies with a filter before call enforce?