Print script errors to disk if a script is open in external editor
complete
WolfGang Senizen
If a script is open in the external editor, print errors the client receives to a matching .log file.
This would allow external tooling to pick them up and display them in editor.
In the future with more advanced errors this could include source map support etc.
Suggestion
- Client receives script error (be it on debug channel, or a compile error)
- Checks if script the error belongs to is open
- Checks if that script is open in external editor
- Appends error to matching file sl_script_<script_name>_<uuid>.luau.log
Log In
H
Harold Linden
complete
This was rolled out as part of a viewer update
H
Harold Linden
inĀ progress
Viewer folks said that compile errors are doable, routing runtime errors to the file would be kind of janky, and will probably come in some form later.
We really need to figure out some kind of proper editor / debugging bridge API for that sort of work.
H
Harold Linden
tracked
H
Harold Linden
underĀ review
H
Harold Linden
Hmm, this might be tricky. I don't believe the error reporting mechanism includes the
script
ID in the error, so it'd have to parse out the script name from the error message, and try to see if there's a script open with that name in the error's object ID.I'll ping the viewer devs and see what they think.
WolfGang Senizen
Harold Linden
I forgot to make it clear in the original post, but compile errors too.