Skip to content

Fix to issue #510 Watch doesn't detect cascading changes when nospawn is true#512

Open
bchabrier wants to merge 6 commits intogruntjs:mainfrom
bchabrier:master
Open

Fix to issue #510 Watch doesn't detect cascading changes when nospawn is true#512
bchabrier wants to merge 6 commits intogruntjs:mainfrom
bchabrier:master

Conversation

@bchabrier
Copy link
Copy Markdown

@bchabrier bchabrier commented Jun 3, 2016

This fixes issue #510, by keeping the watchers when the task is running (i.e. when nospawn is used). In spawn mode, the watchers are closed and recreated as before.

I have added a test suite in nospawn_test.js, which uses grunt-contrib-copy. The test creates a source.js file, which is copied into destination.js. Without the fix, the creation of source.js is correctly detected by watch, not the creation of destination.js.

The full test suite passes on travis, but erratically fails on windows (interrupt).

Hope that helps!

@judowalker
Copy link
Copy Markdown

Is anybody going to merge this?

@ArmorDarks
Copy link
Copy Markdown

Hello?

@xgiovio
Copy link
Copy Markdown

xgiovio commented Feb 14, 2018

Why is this still open?

Base automatically changed from master to main March 22, 2021 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants