Treat agent-suggested any / as casts on UI props as a merge blocker
The component compiles. That’s because the agent wrote props as any , or value as string , or sprinkled // @ts-expect-error on a that now takes a number . The runtime still blows up when the form submits "" . I’ve started treating new any / as on UI props as a merge blocker, not a typing nit. The c…
Read the full story at DEV Community — AI ↗
Timeline · 1 report
- 2026-11-12 15:37 · DEV Community — AI
Treat agent-suggested any / as casts on UI props as a merge blocker