Keep traces of other extensions in the blueprint between runs
Context
- As a blueprint editor creating a multi-extension blueprint, I want to be able to co-develop to extensions that communicate with each other
- Currently PixieBrix will clear the trace of other extensions when I re-run an extension
- We had implemented logic to clear traces when switching between extensions in the page editor to avoid stability problems due to accumulating lots of trace data
Implementation Sketch
- Track blueprint id in trace
- Don't clear traces from the same blueprint
Related
- https://pixiebrix.slack.com/archives/C02CN01JXAA/p1661808241160789
This issue will be closed in 7 days unless the stale label is removed, or a comment is added to the issue.
Keeping traces may cause memory problems without: https://github.com/pixiebrix/pixiebrix-extension/issues/3897
This issue will be closed in 7 days unless the stale label is removed, or a comment is added to the issue.
Given that we're now creating mods with multiple triggers, etc. This is important for development. We'd just want to likely keep the trace from the latest run of each
This issue will be closed in 7 days unless the stale label is removed, or a comment is added to the issue.