jq
jq copied to clipboard
Improved development experience
This issue is meant to collect ideas for an improved development and debug experience.
Some ideas:
- Option to enable some kind of stack trace on error
- Function name if
defor builtin - Filename, line and column
- Possible to even show some lind of shorten binding/args?
- Function name if
- Improved errors
- For builtins include function name
- For error thrown by
def/lambdas track name/location also somehow to be shown if not caught?
A debugger would be nice too...
Like in Python's pdb, we could have a breakpoint builtin that drops one into a debugger prompt where . and bindings could be examined. Being able to step in and so on would also be nice.