Hello, I have carefully investigated your case and realized that this issue was addressed before. If you just remove the :: separation, the problem should be solved. Here is the related issue and documentation references.
Thank you for your cooperation.
Thank you for providing extra details. Currently, we do not have an option to customize this text. You can follow the next releases to be able to customize it.
May I ask for your license type?
Hello, I recommend you to follow this documentation part to customize the AuthWrapperComponent. The auth wrapper component comes from @volo/abp.ng.account/public , so you can import it like this:
import { eAccountComponents } from '@volo/abp.ng.account/public';
Hello, since then we have published the previous patch recently, we will be releasing the next one in the upcoming week.
I am pleased to hear that. Additionally, I will be addressing the other import issue as well. So, you can follow this issue within the releases 🙏If you prefer a workaround, you can replace the wrong imports with this @volo/abp.ng.text-template-management/proxy
I could not duplicate the same problem unfortunately
Hello, I have carefully checked your case and one of the import problem was solved by this PR previously. I can suggest you to use related DTOs in the Application layer rather than the ones inside the domain. You can follow these documentations as a reference
https://abp.io/docs/latest/framework/architecture/best-practices/application-services
https://abp.io/docs/latest/framework/architecture/domain-driven-design/application-services#object-to-object-mapping
Hello, I have carefully checked your case and I could not duplicate the same problem for the abp packages as you may find in this screenshot.
If you still face the same problem, that would be the best to confirm that these lines are the same in this file angular\node_modules\@abp\ng.schematics\utils\model.js
If this is not the case, there should be a problem with the related upgrade.
Hello,
I apologize for the delay in my response. I have thoroughly investigated the issue you reported but was unable to replicate it on my end. Given this, I recommend upgrading your application to version 8.0, which is more stable and well-supported.
Thank you for your understanding.
