Do we violate the rules in terms of DDD by giving the X.HttpApi.Client reference to Y.Domain or is it a basically dependency issue that we should think about?
This violates the rules, generating a static proxy is the recommended way
I need to add X.HttpApi.Client reference to Y.Domain
No, you don't need. you can generate proxy scripts in any project(even domain project).
For example:
Other steps are needed:
*generate-proxy.json file as an embedded fileIs it best practice to consume X module API on domain layer by referencing X.HttpApi.Client?
yes, this is not the best practice.
If it is not the best practice, should we call remote service on application layer by referencing X.Application.Contracts to Y.Application.Contracts?
Calling the remote service essentially uses Httpclient to send HTTP requests, You can use them at the domain layer or application layer, but you need to care about the dependencies between modules. you can generate static proxy scripts for domain project, everything required class interface and DTO have been generated locally, and you don't need the module reference.
Hi,
You can use the static proxy system: https://docs.abp.io/en/abp/latest/API/Static-CSharp-API-Clients
With Contracts generate all the classes/enums/other types in the client side (including application service interfaces) , This is also the default behavior of the generate-proxy command.
Hi,
Yes you can: https://docs.abp.io/en/abp/latest/UI/Angular/Theming#user-menu
Hi,
We have no plan yet.
You can download source code, it contains css and html code, you can use them to create angular components
https://docs.abp.io/en/commercial/latest/themes/lepton-x/index#source-code
Hi,
It will be available in version 7.4 https://support.abp.io/QA/Questions/5525/How-to-make-a-string-property-that-is-not-null-but-not-required-ie-empty-string-allowed
Hi,
We will create an internal issue for this.
Hi,
Could you share the application error logs?
Hi,
A tenant resolver should set context.TenantIdOrName if it can determine it. If not, just leave it as is to allow the next resolver to determine it.
https://docs.abp.io/en/abp/latest/Multi-Tenancy#custom-tenant-resolvers
