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.
Allow to chain conversions
See original GitHub issueFor use-cases similar to the one mentioned here it would be nice if (implicit) convert() calls could be chained like so: .convert { File(it).expandTilde().path }.file()
As this seems to be a serious breaking change, I wonder if things would be easier if another function, like changeValue(), would be introduced for this purpose that is not allowed to change the type.
In any case, it’s misleading currently that something like .convert { File(it).expandTilde().path }.file() compiles and runs, but silently ignores the first (explicit) conversion. Can we throw an exception if an existing conversion gets replaced?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 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
Good catch; I updated the changelog and release notes.
I was was thinking the same thing; the expansion was a bit of a hack.