ABP 10.7 AI Management installation causes invalid Angular proxies for ActionResult and ChatRole #10948

3 Answer(s)

• 

  0

  AI-Bot created 6 hours ago

  Support Team ABP Agent

  • What you’re seeing is coming from the Angular proxy generator trying to translate some problematic server-side types that the AI Management module exposes in its HTTP API contract (via /api/abp/api-definition?includeTypes=true). In ABP 10.7, those types end up producing invalid TypeScript in the generated models.ts files:

    • Duplicate / conflicting ActionResult declarations (non-generic + generic with the same name).
    • ChatRole being emitted as interface ChatRole extends any, which is invalid TypeScript.

  • There isn’t a supported switch to say “keep module backend/UI functionality but don’t generate its client-side types when I run the default abp generate-proxy -t ng”. The supported approach is to generate proxies per module when you need them, instead of generating everything into the main app proxies.

  • Supported workaround (recommended): generate only the AI Management proxies separately

    1. Remove (or revert) the broken generated proxies in your main app proxy folder (since they are already invalid TS).
    2. Generate only AI Management proxies using the module-scoped command:

  abp generate-proxy -t ng --module aiManagement
  

   This is the documented way to generate the AI Management module’s Angular services/models.
  

  • If you want to avoid pulling AI Management contracts into your default app proxy output, keep using the default generation for your app module:

  abp generate-proxy -t ng --module app
  

  and generate AI Management only when/where you need it using the --module aiManagement command above.

  • If you must generate everything in one shot (single proxy tree), then the only reliable workaround is manually fixing the generated TypeScript after generation (but that is not a stable/supported workflow because regeneration will overwrite).

  Sources (validated)

  • https://abp.io/docs/10.7/modules/ai-management/
  • https://docs.abp.io/en/abp/latest/UI/Angular/Service-Proxies

  ---

  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.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  rshapiro created 4 hours ago

  Getting an error with the command abp generate-proxy -t ng --module aiManagement. Found that this is not the correct module name and used ai-management as the module name but now getting the same ActionResult and ChatRole errors and even more now related to the ai management workspaces. Is this functionality actually production ready?

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel
• 

  0

  maliming created 6 minutes ago

  Support Team Fullstack Developer

  Hi,

  The chat controller in the AI Management client package (ChatCompletionsController) ends up in your app proxies. The invalid ActionResult and ChatRole types come from it.

  You don't need to generate proxies for AI Management. The @volo/abp.ng.ai-management package already ships them (@volo/abp.ng.ai-management/proxy).

  For now, you can hide this controller from the API definition. The endpoint keeps working, the AI Management Angular UI calls it by URL. It's only hidden from Swagger and proxy generation.

  Add this class to your HttpApi.Host project:

  using Microsoft.AspNetCore.Mvc.ApplicationModels;
  using Volo.AIManagement.Client.Controllers;
  
  namespace YourCompany.YourProject;
  
  public class HideChatCompletionsControllerConvention : IControllerModelConvention
  {
      public void Apply(ControllerModel controller)
      {
          if (controller.ControllerType != typeof(ChatCompletionsController))
          {
              return;
          }
  
          controller.ApiExplorer.IsVisible = false;
          foreach (var action in controller.Actions)
          {
              action.ApiExplorer.IsVisible = false;
          }
      }
  }
  

  Then register it in ConfigureServices of your HttpApi.Host module. The module file needs using Microsoft.AspNetCore.Mvc; and using Microsoft.Extensions.DependencyInjection;:

  Configure<MvcOptions>(options =>
  {
      options.Conventions.Add(new HideChatCompletionsControllerConvention());
  });
  

  After that:

  1. Delete the src/app/proxy folder in your Angular app. Its generate-proxy.json remembers that you generated ai-management, so it gets generated again on every run.
  2. Restart the host and run abp generate-proxy -t ng again, without --module.

  We'll fix the controller in the next release. Your ticket has been refunded.

  Thanks

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel