.watchmanconfig changes not picked up - possible solution

[benallfree]

I see this from the watchman docs:

Changes to the .watchmanconfig or /etc/watchman.json files are not picked up automatically; you will need to remove and re-add the watch (for .watchmanconfig) or restart watchman (for /etc/watchman.json) for those changes to take effect.

In order to get config changes picked up, I have to do a watchman watch-del /path/to/my/root and then I can call wml s again.

My question is... is there any harm in wml s doing an auto watch-del first? What would be the downside to this?

[benallfree]

PS, this simple change to watchProject seems to do the trick of re-creating the watch each time, thus picking up any .watchmanconfig changes:

'use strict';

var Q = require('q');

module.exports = function (params) {
	var deferred = Q.defer();

	params.client.command(['watch-del', params.src], (error, resp) => {
		if (error) {
			deferred.reject(error);
		} else {
			params.client.command(['watch-project', params.src], (error, resp) => {
				if (error) {
					deferred.reject(error);
				} else {
					deferred.resolve(resp);
				}
		
			});
		}

	});


	return deferred.promise;
}