Set up dependOn task only if project is affected #240
Merged
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.
Fixes #223
This change will reduce the amount of task that needs to be configured.
The idea is this. When a task doesn't have to run, and if we know it. There is no need to depend on that task and skip it later. The plugin can only depend on the task that should run.
I couldnt now how to test it but I compared change in our project.
Before the change of this pr, tasks that belong to modules that has no change or not affected also created but skipped.
After this change, tasks from unaffected modules are not created.
Any pre task that depends on actual task we are calling also being executed in original implementation.
After the change, you can see that only affected modules tasks are created and called.
(Change is in in-app-notification module)