Add file output, clean up stack traces, and update docs#42
Merged
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
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.
Changes
AI Disclosure: I was really hoping AI would be able to handle adding the file output, but even with prompting it could not re-use the existing formatter cleanly. In the end, I wrote most of the code for it and the docs. AI wrote many of the test cases and helped looking into the debug module. Also, AI could not get to the bottom of the Lua 5.1/LuaJIT issue and I had to step in to debug it.
It truly does sometimes seem great and other times feel severely lacking. Like it can do easy tedious things, but not think clearly.