Activities of "ageiter"

• ABP Framework version: v5.3.0
• UI type: Blazor Server
• DB provider: EF Core

Situation: We have many entities which we want to create via ABP Suite. For each entity a folder is created. This makes the project very confusing. Therefore we have moved the entities into subfolders.

Problem: If we now make changes to existing entities, the ABP Suite does not notice that the entity already exists, because it is not in the usual folder. So the file is created again and you have to merge the changes manually, which is inconvenient. Is there a better option? Is there a way to define in which subfolders the entities are located?

Wish for the future: A possibility to group logically related entities in the ABP Suite. This can also be realized in such a way that we could define a parent folder for each entity. Such a grouping could also be included in the namespace.

• ABP Framework version: v5.3.0 (Stable)
• UI type: Blazor-Server
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): no
• Exception message and stack trace: -

Steps to reproduce the issue:

1. Use ABP Suite to generate entities
2. Create 2 navigation properties to the same entity
3. Go to "Advanced" and change "Property Name" in section "3 Others" to a meaningful name
4. Save and generate the code

Current result: The properties with the foreign key (Guid) are generated correctly with my specified name. But in the classes with postfix "...WithNavigationProperties" and "...WithNavigationPropertiesDto" the entity name is used and numbered. It would be desirable that the chosen name would be used there as well.

My expectation: In all classes where this property is used, my chosen name will be used as property name. The property name chosen for the foreign key should also be used for the navigation property (without the "Id" postfix). If necessary to define separatly with another field in the ABP Suite form.

Example: The class "Book.cs" should have two navigation properties to "Author.cs": MainAuthorId & CoAuthorId

Result in BookDto.cs, Book.cs, ...

public Guid? MainAuthorId { get; set; } 
public Guid? CoAuthorId { get; set; }

Result in BookWithNavigationPropertiesDto.cs / BookWithNavigationProperties.cs:

using BookStore.Author;
using BookStore.Author;

public Author Author { get; set; } 
public Author Author1 { get; set; }

The other bug is that the "using" is added twice (as seen above). I have seen this several times and would find it useful to check if the "using" is already present before adding it.

I hope my concern has been explained in an understandable way.

Thanks, Adrian