.getModule() and .getModules() doesn't include a search on the target node about conditioner

[rikschennink]

I've ran into this problem in my own projects as well. But, I've setup the getModule(s) function to match the behavior of the querySelector which also searches within a given context and does not take the supplied context into account.

The develop branch contains a version of Conditioner where I tried to remedy this problem without automatically searching from the parentnode. See the updated getModule function description below.

/***
 * Returns the first [ModuleController](#modulecontroller) matching the supplied query.
 *
 * - `getModule(element)` get module on the given element
 * - `getModule(element, path)` get module with path on the given element
 * - `getModule(path)` get first module with given path
 * - `getModule(path, filter)` get first module with path in document scope
 * - `getModule(path, context)` get module with path, search within context
 * - `getModule(path, filter, context)` get module with path, search within matched elements in context
 *
 * @method getModule
 * @memberof Conditioner
 * @param {...*=} arguments
 * @returns {(ModuleController|null)} module - The found module.
 * @public
 */

[mark-ettema]

That solution is will do! When can I expect a release with this feature?

[rikschennink]

I'm working on Conditioner the coming weeks so expect a small update soon.