sebnitu / vrembem / 11487963411

94%

main: 100%

push

github

Provide context object as an argument in lifecycle hooks (#2090)

To help improve the API of lifecycle hooks, this PR updates arguments so that there is always a "context" object provided as the argument. This removes the need to call methods using `call(this)` or `bind(this)` since whatever you expect `this` to be, it can be more explicitly accessed via the context object. This takes the following form depending on which hook is being run:

```js
{ parent, entry, plugin }
```
- Parent: this is the root component class (Modal, Drawer, Popover, etc). It is always provided to all lifecycle hook calls.
- Entry: this is the current entry object being acted upon. This is provided only when an entry context is available, e.g: `onMount`, `beforeRegister`, `afterRegister`.
- Plugin: this is the plugin object that is running the hook. For example, any hook or `onChange` callbacks will have this context available.

**Additional changes**

- `maybeRunMethod` has been refactored to no longer set `this`, but instead takes an `obj` argument.
- `debug` has been expanded to provide more control and information of log output.
- `condition` options in both `propStore` and `debug` can now either be a boolean value or a function that returns a boolean.

678 of 678 branches covered (100.0%)

Branch coverage included in aggregate %.

101 of 101 new or added lines in 10 files covered. (100.0%)

2436 of 2436 relevant lines covered (100.0%)

136.71 hits per line