Activities of "roberto.fiocchi"

• ABP Framework version: v8.1.0-rc.2
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace: none
• Steps to reproduce:

1. Create a new Abp 8.1.0-rc.2 project using Blazor webassembly
2. With Abp suite create a test entity called "Book" with a property string "Title"
3. Add a couple records using the generated page
4. In the generated page open the "Advanced filters" section and type the following characters "&%;" in the "Title" filter
5. Open the web browser dev tool and press the "Export to excel" button
6. Notice how in the call to the api the filter did not work as intended and the call has returned a excel file with all the record unfiltered

This is due to the filters not getting encoded when the excel api is called.

Add comments or explanations to the implemented fix Example https://commercial.abp.io/releases/pr/16778

It would be nice to have a couple lines of description on what was done for each commit https://commercial.abp.io/releases/tag/8.1.0-rc.2

No, that's not what I want: I already know the top-menu layout, but that's not what I meant.

I want to add this feature in side menu layout Keeping the "side-menu layout" I want to move the toolbar on top and keep the menu on the left. The request is similar to this ticket (but I use blazor WASM instead of Angular): https://support.abp.io/QA/Questions/3746/LeptonX-Theme-Main-Header-Toolbar-in-Top-Main-Header-together-with-Main-Menu-in-Left-Sidebar

• ABP Framework version: v8.1.0-rc.1
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): no
• Exception message and full stack trace:
• Steps to reproduce the issue:

For LeptonX Theme for Blazor WASM, is it possible to have the right toolbar at the top while keeping the main menu in the left sidebar (to mimic the old Lepton Theme layout)?

We would like to have the same layout and features of ASP.NET ZERO, with the notification component (having the unread notification indicator) and the message component (with the unread message icon) inside the toolbar

By clicking on the notification icon we would like to have a component like the one present in aspnet zero. How could we implement these features (including the notification service inside that)?

We would also like the chat UI to replicate the one present in ASP.NET ZERO, therefore a disappearing chat on the right side. Is it possible and how?

Using Blazor Wasm: Add a background worker to periodically clean old/expired audit logs from the DB, a feature already present in AspNetZero https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Features-Angular-Audit-Logs#periodic-log-deletion

A couple of suggestions for abp suite:

1. When a string attribute in a entity has "Required" checked but "Allow empty string" unchecked the generated code for the entity has the wrong check in the entity's contructor: It uses "Check.NotNull" that will still allow empty strings to pass even tho we dont want them In the Manager this is already correct since it uses "Check.NotNullOrWhiteSpace" which will not allow empty strings
2. Make it so that abp suite still works when not connected to a network, it failes to get login-info and it wont start
3. Abp suite as of now doesn't allow a string attribute to have the same minimum length and maximum length, it would be useful to have this feature since some attribute might have a fixed length.

Would be nice to be able to download all the templates in Abp Suite without having to modify each one manually to retrieve it, this would help to notice the differences in the templates in newer versions. Ref: https://docs.abp.io/en/commercial/latest/abp-suite/editing-templates

https://support.abp.io/QA/Questions/3052/Your-feature-request#answer-3a0d62be-d186-9460-0995-e613ddc33fbf

I would like the advanced filter to be generated optionally (for all UI types)

Thank you

This works:

protected List<PermissionGrantInfoDto> GetChildPermissions(PermissionGroupDto permissionGroup, PermissionGrantInfoDto permission)
{
    var childPermissions = new List<PermissionGrantInfoDto>();
    GetChildPermissions(childPermissions, permissionGroup.Permissions, permission);
    return childPermissions;
}

protected void GetChildPermissions(List<PermissionGrantInfoDto> allChildPermissions, List<PermissionGrantInfoDto> permissions, PermissionGrantInfoDto permission)
{
    var childPermissions = permissions.Where(x => x.ParentName == permission.Name).ToList();
    if (childPermissions.Count == 0)
    {
        return;
    }

    allChildPermissions.AddRange(childPermissions);

    foreach (var childPermission in childPermissions)
    {
        GetChildPermissions(allChildPermissions, permissions, childPermission);
    }
}

hi,

It seems to me that as of today this is a requirment since the permission modal wont work properly if it isn't respected, What is the point of having the PermissionDefinition.AddChild() function and nesting them if the rest of the implementation doesn't use this structure?