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.
get { ... } auto-descriptions do not work on windows
See original GitHub issueHi,
strikts feature to display the actual code passed into a get { thisAndThat } is extremely useful. It’s also okay to display the object value as a fallback if the resolver doesn’t produce a result. However, under windows, the resolver fails very often for a simple reason:
FilePeek.kt, lines 30 - 36: Here you check for things like "/out/", but when running under windows, the variable classFilePath contains backslashes (\) instead as separators.
Could you please replace the hard-coded / characters by File.separator to make it work under windows too?
Thanks.
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (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
You’re absolutely right; I didn’t notice that this class belongs to a different package when I was looking through the code. I’ll forward the issue to that package.
@christophsturm no worries, the PR was just created a couple of hours ago. I reported the windows issue on your repo a while back, and since I got no response I decided to take action on my own. Thanks for releasing the new version!