Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It started with eslint in VS Code being more antsy about TypeScript issues recently. So I drafted a set of guidelines and rules on how to port from JavaScript to TypeScript and let GPT 5.4 as well as Claude Opus 4.6 do the heavy lifting.
Each commit represents an iteration of Opus 4.6 coming up with what to port next and GPT 5.4 doing the leg work and me smoke testing and reviewing the code each time. Sometimes I had to git reset between commits, because the code was rendered unusable or the porting effort were too complicated.
The biggest issue the LLMs agents had were to work the way around some quirky JavaScript code the code base employs: Variables changing type, dealing with detecting at run time what to do next etc. GPT 5.4 loves to introduce helper functions to deal with recurring TypeScript casting and it loves to chain casts with types/interfaces together with anonymous types. Multiple times I had to remind it to not introduce unnecessary function calls in hot code paths.
On a positive note: A few bugs have been spotted and fixed as well, no more too verbose code with JSDoc syntax and no more red markings all over the place due to static analysis predicting issues such as accessing missing properties or potentially run into nulls and undefineds.