TJ
TJ
I think nanoseconds is far too much granularity for the average use-case, I've never had a problem with millisecond resolution, but it's a breaking change.
logging is really a subset of tracing, and the opentracing API is pretty nice, certainly nothing to complain about. I think it would be great to have apex/log "2.0" effectively...
If you are unmarshaling from JSON you can just pass it to the handler, but if you don't have direct access to the handler we need another method for that.
Set a reasonable default and then grow accordingly, instead of defaulting to a pretty large offset which looks kind of silly in simpler cases.
I'm contemplating a 2.0, I have some features in mind of course, but I'd love to hear what people would like to see if you could have anything at all...
Not feeling up to the 4.5gb xcode right now hahah, but it would be great to support!
https://apex.sh/ping/ will always be a more premium service but we can provide the basics here. - [ ] add - [ ] document
Currently you have to do `up logs | cat` to trigger the !isatty() condition, but there should be a flag