[CLI MCP] Invalid chartType enum value ("Bar") generated in category chart

[viktorkombov]

Ignite UI CLI Version

15.0.0-rc2

Framework

Angular

CLI Command

ai-config

Node.js Version

24.2.0

Operating System

Windows

Package Manager

npm

Description

When generating category charts with Claude Sonnet 4.6, the chartType is sometimes set to "Bar", which is not a valid member of the expected enum.

This leads to a runtime error:

`ERROR Error: Invalid CategoryChartType value: Bar

Steps to Reproduce

1. Generate a cateogry chart using the follwing prompt:

15-rc.2-prompt1.md

Actual Result

chartType is set to "Bar" and the app throws a runtime error.

Expected Result

Only valid FinancialChartType enum values should be generated.

Error Output / Logs

ERROR Error: Invalid CategoryChartType value: Bar

Additional Context

No response

[kdinev]

@viktorkombov Could you run ig --version? Are you on RC.1? Also, how did you get around the bug template?

[viktorkombov]

@kdinev Sorry — I created the issue using the “Blank issue” option instead of the bug template. I can close this and reopen it using the proper template if you prefer.

Also, I’m currently on version 14.9.2.

[kdinev]

@viktorkombov That's the local version of the cli. Globally do you have 15.0.0-rc.0 or .1?

[viktorkombov]

@viktorkombov That's the local version of the cli. Globally do you have 15.0.0-rc.0 or .1?

@kdinev 15.0.0-rc.0

[kdinev]

@viktorkombov That's the local version of the cli. Globally do you have 15.0.0-rc.0 or .1?

@kdinev 15.0.0-rc.0

Update to .1 and see if you get the same behaviour. I implemented fixes with .1, which are in updated skills that come with .1

[viktorkombov]

Update to .1 and see if you get the same behaviour. I implemented fixes with .1, which are in updated skills that come with

@kdinev I updated to .1 and tested again with the same prompts. Тhe issue is no longer reproducible. It looks like the fixes resolved it. Closing this issue.

[viktorkombov]

Reopening this issue as the behavior is still reproducible.

Although updating to 15.0.0-rc.2 initially appeared to resolve the problem, I’m still encountering it intermittently (not on every run, but it does occur under certain conditions).

I’ll include a prompt below that can be used to reproduce the issue:

15-rc.2-prompt1.md