Activities of "papusa"

Thank you

Hi!

When provideThemeLeptonX() is used with withThemeLeptonXOptions(), the settings menu shows hardcoded English labels (e.g. "General Settings", "Language Options") instead of localized strings from the LeptonX resource, even when translations exist on the backend.

Steps to reproduce:

• Configure LeptonX with theme options:

provideThemeLeptonX(
  withThemeLeptonXOptions({
    defaultTheme: 'dim',
  }),
),

• Switch the UI language to Swedish (or another non-English locale).
• Open the settings menu (gear icon).
• Observe that "General Settings" and "Language Options" remain in English.

Root cause looks like a provider order issue: withThemeLeptonXOptions causes DefaultTranslateService to override AbpTranslateService.

I found a workaround, re-registering the ABP translate provider after provideThemeLeptonX(...) is solving the issue:

provideThemeLeptonX(
  withThemeLeptonXOptions({ /* ... */ }),
),
LPX_TRANSLATE_PROVIDER,

However, I think it still should be fixed on ABP side.

Thank you!

There are no providers on feature groups, only on individual features. However, after filtering out features that are not valid for the current provider, a group can become empty and still be shown in the UI.

I think that is also an issue: empty feature groups should be hidden after provider-based feature filtering. Just for your information, I have already fixed this on my side within my FeatureAppService replacement.

Thank you!

I would consider this a bug, not only a UX mismatch. If AllowedProviders = ["T"], the Edition Features UI should not allow saving an "E" value that runtime feature checking will ignore. The UI/API should respect FeatureDefinition.AllowedProviders for the provider currently being edited.

n ABP 10.1.1, a feature defined with .WithProviders(TenantFeatureValueProvider.ProviderName) still appears in the SaaS Edition Features dialog and can be saved for provider E. However, runtime IFeatureChecker appears to filter value providers by FeatureDefinition.AllowedProviders, so edition values for that feature are ignored and only tenant values are considered.

Could you clarify whether AllowedProviders is intended to restrict only runtime feature value providers, or also Feature Management UI/API providers? If it is runtime-only, should the Edition Features dialog hide or disable features whose AllowedProviders does not include E, to avoid saving values that runtime checks will not use?

I can't access it, I've sent a request to get it.

Hi,

I can also share a sample project containing a fixed version if you prefer.

Yes, that would be great if it's possible.

Thanks for response!