Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds 'watch-start' and 'watch-end' events #440

Closed
wants to merge 1 commit into from

Conversation

haroldtreen
Copy link

Built the functionality I was looking for in this issue: #437

Changes make grunt events to be emitted for:
watch-start: Fires right before watch tasks begin
watch-end: Fires right after all tasks have completed

@@ -1,4 +1,4 @@
# grunt-contrib-watch v0.6.1 [![Build Status: Linux](https://travis-ci.org/gruntjs/grunt-contrib-watch.png?branch=master)](https://travis-ci.org/gruntjs/grunt-contrib-watch)
# grunt-contrib-watch v0.7.0 [![Build Status: Linux](https://travis-ci.org/gruntjs/grunt-contrib-watch.png?branch=master)](https://travis-ci.org/gruntjs/grunt-contrib-watch)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dont change this, it is autogenerated

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this was updated for the purpose of our fork. The first commit is probably the only one needed and versioning can be handled whenever you guys do the next release.

@haroldtreen
Copy link
Author

Addressed comments @eddiemonge. Let me know if you need anything else 👍

@eddiemonge
Copy link
Contributor

You should squash your commits down to one

@haroldtreen
Copy link
Author

Squashing complete

@@ -203,7 +203,7 @@ Set `options: { cwd: { files: 'a/path', event: 'a/path' }}` to strip off `a/path


## options.livereloadOnError
Type: `Boolean`
Default: `true`
Type: `Boolean`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These trailing spaces are needed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why? why doesnt 197 have them?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 trailing spaces = line break in markdown.

The fact that it's missing in line 197 doesn't mean it should be removed here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And in fact it's not missing in line 197; I fixed those the other day 2345454

@haroldtreen
Copy link
Author

Whitespace restored

@daniyel
Copy link

daniyel commented Aug 16, 2017

What is with this pull request? Did this 'fix' got implemented in some other commit?

@XhmikosR
Copy link
Member

Unfortunately this needs to be rebased and I can't seem to be able to push on @haroldtreen's fork.

@haroldtreen
Copy link
Author

I don't need this anymore, so I'll close.

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.

None yet

4 participants