- Template: microservice
- Created ABP Studio Version: 1.0.1
- Current ABP Studio Version: 1.2.2
- Multi-Tenancy: Yes
- UI Framework: mvc
- Theme: leptonx
- Theme Style: system
- Theme Menu Placement: side
- Database Provider: ef
- Database Management System: postgresql
- Mobile Framework: react-native
- Public Website: Yes
- Include Tests: Yes
- Dynamic Localization: Yes
- Kubernetes Configuration: Yes
- Grafana Dashboard: Yes
- Use Local References: No
- Selected Languages: English, English (United Kingdom), 简体中文, Español, العربية, हिन्दी, Português (Brasil), Français, Русский, Deutsch (Deuthschland), Türkçe, Italiano, Čeština, Magyar, Română (România), Svenska, Suomi, Slovenčina, Íslenska, 繁體中文
- Default Language: English
- Create Command: abp new TavTechnologies.Treva -t microservice --ui-framework mvc --mobile react-native --database-provider ef --database-management-system postgresql --theme leptonx --skip-migrator --public-website --dont-run-bundling -no-language-management -chat -file-management
After we upgrade to 9.3.3 and abp suite to 1.2.2 we have an issue. As i understand, there is a fix in %%entity-namespace%% variable in templates and now, we have issues when we update entitites with abp suite. Belows are just example.
As you can see there is a new word in %%entity-namespace%% or in %%microservice-entities-namespace-prefix%%.
How can we find where these values are set?
2 Answer(s)
-
0
The %%entity-namespace%% and %%microservice-entities-namespace-prefix%% template variables in ABP Suite are calculated based on the entity's location and the project structure. In recent ABP Suite versions (including 1.2.2 and ABP 9.3.x), there was a fix to make these namespace calculations more accurate and consistent, especially for microservice solutions.
- The value for %%entity-namespace%% is now derived from the actual folder structure of your entity files. For example, if your entity is under
Entities\BtaApiShop\DetailMappings, the namespace will be...Entities.BtaApiShop.DetailMappings. - The value for %%microservice-entities-namespace-prefix%% is also based on the folder path and project root, ensuring that generated code matches the physical structure.
You can see these values in the generated code and in the
.jsonfiles under thesuite/entitiesfolder. If you want to adjust or review how these are set:- Open the relevant entity's
.jsonfile insuite/entities. - The namespace is determined by the "Namespace" property, which is auto-calculated by ABP Suite based on the entity's folder.
If you have custom requirements for namespaces, you will need to manually adjust the folder structure or the generated code after using ABP Suite, as the calculation is now standardized and not user-configurable from the UI.
This change was made to fix inconsistencies and ensure that generated code compiles correctly with the expected namespaces.
No verified source available for this specific query.
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
- The value for %%entity-namespace%% is now derived from the actual folder structure of your entity files. For example, if your entity is under
-
0
But everytime when we update an entity we need to make change at least 30 place. Can you help please?
