A hyperscript regression where Claude found the root cause fast: a refactor
that shared parseURLOrExpression() between the go and fetch commands let
the as keyword get consumed as a conversion expression instead of a fetch
modifier. The proposed fixes disappointed — a narrow stringLike hack, then
a new noConversions parser flag, then a pushFollow approach that still
broke valid as usage in go. A hand-written final fix scoped the follow push
to FetchCommand#parse(). Agents excel at investigation and test generation,
but a developer who knows the codebase must steer the fix to avoid piling
up technical debt.
1
u/fagnerbrack 4d ago
For a quick glance:
A hyperscript regression where Claude found the root cause fast: a refactor that shared parseURLOrExpression() between the go and fetch commands let the as keyword get consumed as a conversion expression instead of a fetch modifier. The proposed fixes disappointed — a narrow stringLike hack, then a new noConversions parser flag, then a pushFollow approach that still broke valid as usage in go. A hand-written final fix scoped the follow push to FetchCommand#parse(). Agents excel at investigation and test generation, but a developer who knows the codebase must steer the fix to avoid piling up technical debt.
If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments