Override component watcher with mounting options

[lmiller1990]

resolves #1391 . We should override a component's watcher if one is provided in the mounting options. The issue explains the bug a bit better and provides an example.

[JessicaSachs]

I thought there might be alternate data structures for watch... Based on the examples here, we need to support: Strings, Functions, Arrays, Objects.

Does includes work as desired with all of those data types?

[dobromir-hristov]

Jess, the key is always a string :)

[afontcu]

LGTM!

Quick question: what would happen if the instance watcher is immediately invoked but the component one isn't (or the other way around)? Would this logic override the value from the instance watcher no matter what?

[dobromir-hristov]

The one you pass to the mount should always override the entire watcher definition, imho. Its up to you, as a dev to take care if its immediate, deep or whatever, no?

[afontcu]

The one you pass to the mount should always override the entire watcher definition, imho. Its up to you, as a dev to take care if its immediate, deep or whatever, no?

Sure! I guess what I wanted to confirm is that the current implementation overrides the entire definion, not only the handler :) I'd assume so, but wanted to make sure 👍