In a model file generated by the abp cli proxy generator, the proxy generator generates a recursive import of the model file itself #10322

2 Answer(s)

• 

  0

  AI-Bot created yesterday

  Support Team ABP Agent

  1. What is happening?

  This is a known limitation of the Angular proxy generator:
  when you have custom classes that subclass PagedResultDto<T> (or other complex generics), the generated models.ts can end up with:

  import type { MyEntityDto } from './models';
  
  export interface MyEntityDto {
    // ...
  }
  

  or similar patterns for generic type parameters (e.g. T, TKey), causing TypeScript errors like:

  • TS2440: Import declaration conflicts with local declaration of 'MyEntityDto'
  • TS2303 / TS2459 about circular definition or missing exported member T, TKey, etc.

  The official support answer for the linked ticket confirms:

  The generate-proxy command may not support all C# types; you need to modify the generated code manually for now.

  So this is a limitation/bug of the proxy generator, not your specific project.

  ---

  2. Recommended fixes / workarounds

  You have two practical options. The recommended one is to simplify the C# DTOs so they’re proxy‑friendly.

  Option A – Change your C# DTO design (recommended)

  Avoid exposing custom subclasses of PagedResultDto<T> in your public application contracts.

  Instead of:

  public class MyEntityDto : EntityDto<Guid>
  {
      // ...
  }
  
  public class MessageCenterCustomPagedResultDto : PagedResultDto<MyEntityDto>
  {
  }
  

  Change your application service methods to return the base PagedResultDto<T> directly:

  public class MyEntityDto : EntityDto<Guid>
  {
      // ...
  }
  
  // AppService method
  public virtual async Task<PagedResultDto<MyEntityDto>> GetListAsync(MyInputDto input)
  {
      // ...
  }
  

  If you need extra properties on the “paged result”, make them normal properties on a non‑generic DTO instead of subclassing PagedResultDto<T>:

  public class MyEntityPagedResultDto
  {
      public long TotalCount { get; set; }
      public List<MyEntityDto> Items { get; set; }
  
      // Any additional fields you need
      public string SomeExtraInfo { get; set; }
  }
  
  // AppService method
  public virtual async Task<MyEntityPagedResultDto> GetCustomListAsync(MyInputDto input)
  {
      // Map manually from a PagedResultDto<MyEntityDto> or query result
  }
  

  This produces simple DTO shapes that the Angular proxy generator can handle without generating recursive imports or bogus generic imports.

  After changing the contracts:

  1. Rebuild the backend.
  2. Run the proxy generator again:

  abp generate-proxy -t ng
  

  3. Build the Angular project.

  You should no longer see TS2440 on MyEntityDto (or similar generic / import issues).

  ---

  Option B – Manually fix the generated TypeScript after each generation

  If you must keep the C# design as‑is, you can:

  1. Run abp generate-proxy -t ng.
  2. Open src/app/proxy/models.ts (and any client-models/models.ts in modules, if applicable).
  3. Manually fix the problematic parts, for example:
     • Remove the self‑import:

  // Remove this line:
       import type { MyEntityDto } from './models';
  

  • Or rename the locally declared interface to avoid name clash and adjust usages.

  4. Then build the Angular app.

  The downside: every time you regenerate proxies, these files can be overwritten, so you must either:

  • keep your changes minimal and easy to re‑apply, or
  • exclude those DTOs from your public HTTP APIs and use separate non‑generic DTOs for Angular.

  ---

  3. Why this happens / what to expect

  • The current generator does not correctly handle:
    • C# types that are subclasses of PagedResultDto<T>.
    • Some generic types used in DTOs (e.g., CompareLookupDto<TKey>, MyEntityCustomPagedResultDto<T>).
  • It tries to treat type parameters or derived generic types as if they were standalone DTOs in the shared models.ts, leading to:
    • recursive imports (import { MyEntityDto } from './models'; while also defining MyEntityDto),
    • or imports of generic parameters (import { T } from '../../../models';).

  Given the current behavior, the most robust, maintenance‑friendly fix is to refactor your application contracts as in Option A so they only use:

  • PagedResultDto<MyEntityDto> directly, or
  • simple DTOs with TotalCount + Items + any extra fields.

  ---

  4. Source

  Support ticket describing this exact behavior and official guidance that generate-proxy does not support all C# types and may require manual fixes:

  • https://abp.io/support/questions/6657/Generation-of-Service-Proxies-for-Angular-not-handling-subclasses-of-PagedResultDtoT-correctly

  ---

  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.

  Save Cancel
• 

  0

  gustavodm created yesterday

  Thanks, option A worked.

  Save Cancel