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.
Builtin "swift build" command invalidates cache for global command
See original GitHub issueWhenever I save a file in an SPM project, swift build will automatically be run. After that has happened, running swift test from my terminal rebuilds all dependencies and the source.
This is not the case if I just run swift build and then swift test straight from my terminal.
I can also see the issue in reverse, that is, after I have run swift build or swift test from the terminal, the build time is much longer in VS Code.
This leads to the very annoying workflow that I save a test file, then wait for everything to be rebuilt from scratch in VS Code, then finally run swift test which again rebuilds everything from scratch, and then runs the tests.
Happy to provide any more information that might be relevant ☺️
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 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
The workaround landed in 2.4.0.
@LinusU I could not find a solution on this by now. As a workaround we could add a new setting to allow passing a custom build path if this issue becomes too big.
This would additionally help others who want to automatically build their tests like https://github.com/jinmingjian/sde/pull/32, too.