أنشطة "EngincanV"

If I can use child entities for multiple levels it would be great.

We have an internal issue for that, but it's in the backlog now. We will try to prioritize it. Regards.

We have previously created entities in this version without encountering such an issue. Will there be any improvements in version 7.1.1?

No, we are not considering to release a patch version for 7.1.1.

Hi, this is an old problem, which is already fixed with v7.2.0-rc.1. So, please update your CLI version, project and Suite and regenerate the entity.

Question 1: How can I use Location datatype with abp suite entity generator ?

Currently, ABP Suite does not support Location datatype.

Question 2: Any example how to include NetTopologySuite with abp.io solution ? If you had any advices on this it is very welcome.

ABP solutions are basically .net solutions, so you can follow the same steps that you would normally do with a plain .net project.

Because the templates are not yet perfect and sometimes contain errors, I had to customize them. When a new version is released, it is relatively time-consuming to find out whether I can switch back to the original template, whether I have to continue using my modified template or whether I should even perform a merge.

Several possible solutions come to mind:

• Easy to implement and already helpful would be to have another button "Show default". Currently you have to select "Revert customization" to see the default.
• Maybe it would also be a solution to store the original file in the same directory with a different file extension (.suite/customized-templates/Frontend.Blazor.Page.Item.razor.original.txt), then you would be able to see very well in Git whether changes have been made in the original (new version) and you would also have the possibility to make a diff with your own changes.
• The "deluxe version" would be if you were to implement a merge tool with which we could update to a new version ;-)

Thanks for the suggestion, I have created an internal issue for this feature request.

I get compilation errors when I have generated master-child entities. I am using version 8.1.0.

I had to remove %%<if:HasMasterEntityNavigationProperties>%% and %%</if:HasMasterEntityNavigationProperties>%% in the following two templates:

• Frontend.Blazor.Page.Partials.Item.razor.ChildEntitiesTabPanels.txt
• Frontend.Blazor.Page.Partials.Item.razor.cs.ChildEntitiesMethods.txt

This does not seem to be applied correctly.

After my change, the entites were generated correctly. The changed result looks like this:

Thanks for reporting this bug. We have already identified the problem and have an internal issue for that. It will be fixed with v8.1.2+.

For a clean look of the extended classes in Blazor, an addition would have to be made in the .filenesting.json file (this is overwritten every time I generate something with ABP Suite...).

Add the following to the extensionToExtension section:

".Extended.razor.cs": [ 
    ".razor" 
  ] 

Done ✅ (It will be included with v8.1.2+)

File is empty

okay, then please make a clean installation by following https://support.abp.io/QA/Questions/414/ABP-Suite-install-problem-How-can-I-reinstall-clean-install#answer-9c56ff0e-0a46-ffd1-dd08-39f78e032607

Can you share your entity metadata, and steps that you done, so I can try to reproduce it?

Please share the appsettings.json file under the %UserProfile%.abp\suite directory.