Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
support sending the underlying vararg to branch trees
See original GitHub issueThis is a potential feature request
With a lot of third party (logging/monitoring/crash) services, there are times when it’s useful to send metadata at a per log level (as against the global user level).
so basically instead of:
protected abstract fun log(priority: Int, tag: String?, message: String, t: Throwable?)
supply the args sent in as well
protected abstract fun log(priority: Int, tag: String?, message: String, t: Throwable?, vararg args: Any?)
This allows branch trees to potentially send the args separately to a service (potentially attaching it as more metadata).
Can add more context, if the use case doesn’t make sense. I think it’s similar to what was brought up here (I think).
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m getting back into Timber soon™. I know it’s been kinda stuck for a while.
Can you add your usecase to #184 in as much detail as you’re able to share?
Kotlin inline functions and deferred lambdas and string templating is coming, but that’s going to be totally separate from “context” arguments. Vararg is kinda terrible because you’re allocating the array and filling its contents even when logging is disabled. And even when it’s enabled, you immediately unpack the array. Bad all around. I don’t want to re-use it for contexts/metadata.