Activities of "maliming"

hi

Please try this.

[Dependency(ReplaceServices = true)]
[ExposeServices(typeof(UserManagement))]
public class MyUserManagement : UserManagement
{
    protected async override Task AddClaimAsync()
    {
        var claim = ClaimsModel.AllClaims.FirstOrDefault(c => c.Name == SelectedClaimType);
        if (claim == null)
        {
            return;
        }

        if (claim.Required && (claim.ValueType == IdentityClaimValueType.String && string.IsNullOrWhiteSpace(SelectedClaimValueText)))
        {
            await Message.Info(L["ClaimValueCanNotBeBlank"]);
            return;
        }

        if (SelectedClaimValueText.IsNullOrWhiteSpace())
        {
            await Message.Info(L["ClaimValueIsInvalid", claim.Name]);
            return;
        }

        if(!SelectedClaimValueText.IsNullOrWhiteSpace() && !claim.Regex.IsNullOrWhiteSpace() && !Regex.IsMatch(SelectedClaimValueText, claim.Regex))
        {
            await Message.Info(L["ClaimValueIsInvalid", claim.Name]);
            return;
        }

        ClaimsModel.OwnedClaims.Add(new IdentityUserClaimViewModel
        {
            ClaimType = SelectedClaimType,
            ClaimValueText = SelectedClaimValueText,
            ClaimValueNumeric = SelectedClaimValueNumeric,
            ClaimValueDate = SelectedClaimValueDate,
            ClaimValueBool = SelectedClaimValueBool
        });
    }
}

hi

What's your lepton package version?

abp&volo 8.2.1, then leptonx should use 3.2.1

hi

Please share your project to liming.ma@volosoft.com via https://wetransfer.com/

Thanks

hi

What's your Lepton package version?

And I think you can ignore this warning. It won't break anything.

hi

https://github.com/abpframework/abp/issues/20145#issuecomment-2202052771

hi

We will fix this asap. Sorry for that.

hi

We will fix this asap. Your ticket has been refunded.

hi

We will fix this asap.

Sorry for that. We will update the document.

hi

You have to enter the full username to find the user.

If an API can query all users, this is a security problem. So we changed the way.