-
### 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.…
-
### Summary
Only having one lifecycle hook per request makes it impossible to use multiple plugins which both set the same hook, or makes it easy to inadvertently break plugins by overriding a hook t…
-
We need to know when our node.js code is about to be put into the background or killed so that we can do things like gently shut down Express, flush data out of RAM onto disk, etc. We should also expo…
-
## Background
We often need to run a small amount of initialization code for custom components, e.g. in bslib for sidebars, cards and accordions. In a static context, we could, in theory, just use …
-
In #931, we added checks to ensure that lifecycle hooks only run once to avoid users accidentally running app.Stop twice by doing: app.Run, app.Stop.
This seems to have broken some users like @zent…
-
## Describe the bug
A clear and concise description of what the bug is.
When I add a `fetch()` and a `created()` hook to a view, the `fetch` hook is called before the `created`.
In a regular N…
-
Runtime SDK Lifecycle hooks are currently linked to Clusters entirely based on a namespace selector defined in an ExtensionConfig. If an ExtensionConfig has a Lifecycle hook enabled and a Cluster matc…
-
This may be a bit of a hack due to my usage but it felt useful enough to bring up (maybe a way to do this exists already)
I've been looking for a way to execute some code _after_ every OnStart hook…
-
Different apps can register the same lifecycle hooks. In most cases, the order of execution does not matter, but sometimes it causes unpredictable results.
For example: If we have 2 Apps, 1 for Aut…
-
This was discussed in Discord, but after I thought about it some more I think it should be given some more thought. Roact will throw very strange, very hard to debug errors if you yield in any lifecyc…