You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To clarify, if we use symlinks not only will the first creation of the merged dir be faster but we also should be able to leave in place any existing links. We only have to delete any links to deleted files and add new ones for new files.
I think we will need to start this as opt-in only, since the main supported use case of the output directory is for deployment.
For the test command we will automagically use the symlink option though, which is the other code path that is affected by this (and the main motivation for fixing it too).
Closes#1242
Added a new `--symlink` option, which is defaulted to true for `test` but no other commands.
This is unfortunately a breaking change in build_runner and build_runner_core as it required adding a new interface which must be implemented by any `RunnerAssetReader`, which is an exposed class from both of these packages.
This would speed up running tests or development scenarios where people need a merged output dir.
The text was updated successfully, but these errors were encountered: