I am unable to reproduce the problem. I created an application with v8.1.1 in ABP Suite, with angular as the UI option and the seperate authentication server option selected, but I could successfully generate CRUD pages without having a problem.
Is it possible that your ABP CLI and ABP Suite versions are not the same?
Hi, I'll check this asap.
Hi, sorry for the late response. But I'm unable to reproduce it:
Please check https://docs.abp.io/en/commercial/latest/abp-suite/create-module-solution#adding-your-new-abp-module-to-your-main-solution
Hi, sorry for the late response. I'll create an internal issue to improve our templating system and format. In the meantime, you can check https://docs.abp.io/en/commercial/latest/abp-suite/editing-templates this documentation for the details of some templates' placeholders.
Hi, thanks for the suggestion. I agree that the child entity should have the same audit level as the base class with its master entity. I'll create an internal issue for that.
Regards.
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.