Description
In some generated outputs, the code mixes component APIs and binding patterns from different libraries instead of using the conventions of the target library consistently.
This can lead to incorrect behavior such as:
reading values from the wrong event shape
using props or bindings that belong to another framework or component model
combining state patterns that conflict with the target component’s internal behavior
producing code that looks valid at first glance but does not work correctly at runtime
The core issue is that generation is not always strict enough about library boundaries. When migrating or building inside a specific stack, the output should follow that library’s event contracts, property model, binding syntax, and state handling rules, rather than mixing assumptions from another library or framework.
Proposed Solution
Update the MCP generation flow so it treats library boundaries more strictly during code generation. Once a target library is chosen, the generated code should consistently use that library’s APIs, props, events, and binding patterns.
Description
In some generated outputs, the code mixes component APIs and binding patterns from different libraries instead of using the conventions of the target library consistently.
This can lead to incorrect behavior such as:
reading values from the wrong event shape
using props or bindings that belong to another framework or component model
combining state patterns that conflict with the target component’s internal behavior
producing code that looks valid at first glance but does not work correctly at runtime
The core issue is that generation is not always strict enough about library boundaries. When migrating or building inside a specific stack, the output should follow that library’s event contracts, property model, binding syntax, and state handling rules, rather than mixing assumptions from another library or framework.
Proposed Solution
Update the MCP generation flow so it treats library boundaries more strictly during code generation. Once a target library is chosen, the generated code should consistently use that library’s APIs, props, events, and binding patterns.