Custom FeatureValueProvider Not Invoked When DefaultValue Is Set in .AddFeature #9243

karl.ettinger@energieag.at created 8 days ago

Hi!

I have implemented a FeatureValueProvider for roles (RoleBasedFeatureValueProvider) and registered it as the first provider in the list of FeatureValueProviders. However, I noticed that when I specify a defaultValue in .AddFeature, my RoleBasedFeatureValueProvider is not invoked. If I leave out the defaultValue in .AddFeature, the text fields of type FreeTextStringValueType appear disabled in the Blazor UI under Administrator → Saas → Editions → Default Edition → Features. This behavior seems quite unexpected. As a workaround, I had to modify my RoleBasedFeatureValueProvider so that, upon the first call to FeatureChecker.IsEnabledAsync, an entry is created in the AbpFeatureValues table.

Could you please explain why my RoleBasedFeatureValueProvider, although registered first in the list, is ignored when a defaultValue is provided in .AddFeature?

Thank you!