Fix execution of before-prepare hooks in a long living process #3140
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When LiveSync operation is started we set
usbLiveSyncService.isInitialized
to true. This variable is used in severalbefore-prepare
hooks.For example
nativescript-dev-typescript
has the following logic:usbLiveSyncService.isInitialized
property is set to true. In this case it does nothing. The idea is that when LiveSync watch process is started, the plugin has startedtsc --watch
process, so there's no need to do anything onbefore-prepare
.However, in a long living process, where the project may be changed, whenever we stop LiveSync process, we must set usbLiveSyncService to false. In case we do not do it, the property remains true and the before-prepare hook of the other project does nothing and the project is not transpiled.