-
hooks should be both per-package and global. something like
```json
{
"scripts": {
"beforetest": "rimraf ./reports/junit",
"beforeeachtest": "mkdir -p $REPO_ROOT./reports/junit/PACKAG…
-
I am trying to log the audit logs, how can i use lifecycle hooks in Menus plugin to achieve the activity logs by user.
-
Loving this lib, finding it extremely useful in our project. As we accrue more and more scripts, we're finding that most scripts share some basic startup/shutdown behaviors, which (in line with the se…
-
Or at least compartmentalize them.
https://github.com/slamdata/purescript-halogen/issues/170
-
It would be useful to be able to run some cleanup code at the end of a run. Examples:
- Tear down a cluster
- Delete a temporary directory
I think it would likely make sense to tie these to resou…
sryza updated
9 months ago
-
## Problem
Sometimes there's a need to run certain function before a record is added or maybe create another record or execute certain workflow after a record is created/deleted (eg: trigger websoc…
-
## Motivation ("The Why")
Sometimes in a project, there is a need to setup the development environment or enforce some policies on dependencies used in the project. However, npm doesn't provide a w…
-
## General
User should have the ability to execute his own scripts on various lifecycle events.
The user should be able to execute his own script on load of the page.
## DoD
* run js script wh…
-
### Current Behavior
Currently, the Extension Page is implemented as a class component, which can be more complex and harder to manage state and lifecycle methods compared to functional components.…
-
This one might require further planning, but for now try and refactor lifecycle methods used to use hooks instead.