feat: introduce standalone execute() and executionTrace() functions and @trace() decorator#54
Conversation
- create a generic `execute()` function that handles async , async and hidden promises function - create standalone `trace()` function usage without requiring engine instantiation. - refactor models⚠️ Deprecation Notice: - `NodeExecutionTrace` is deprecated, Use `ExecutionTrace` instead. - `NodeExecutionTraceExtractor` is deprecated. Use `ExecutionTraceExtractor` instead. - `isNodeExecutionTrace` is deprecated. Use `isExecutionTrace` instead.
Coverage report
Show new covered files 🐣
Test suite run success73 tests passing in 9 suites. Report generated by 🧪jest coverage report action from 2e4d89d |
|
🚫 Unpublished versions: ∅
|
|
🚫 Unpublished versions:
|
a5c9877 to
138acfd
Compare
execute() and trace() functionsexecute() and trace() functions and adapt TraceableExecution to use them
|
🚫 Unpublished versions:
|
execute() and trace() functions and adapt TraceableExecution to use them… functions features: - rename `TraceableExecution` to `TraceableEngine` to separate engine scope from standalone scope - refactor `TraceableEngine` to use the common `trace()` function and the `execute()` behind - doc and generate examples to ensure deprecated engin still work and supported⚠️ Deprecation Notice: - `TraceableExecution` is deprecated and will be removed in a future release. Use `TraceableEngine` instead.
…or execution tracing
138acfd to
c25da94
Compare
…dels and internal utils
c25da94 to
5f70be9
Compare
|
🚫 Unpublished versions:
|
|
🚫 Unpublished versions:
|
execute() and executionTrace() functions and @trace() decorator
c42a84f to
7c165d2
Compare
|
🚫 Unpublished versions:
|
|
🚫 Unpublished versions:
|
7c165d2 to
3567367
Compare
|
🚫 Unpublished versions:
|
69e062d to
32265d0
Compare
|
🚫 Unpublished versions:
|
32265d0 to
7c407ea
Compare
7c407ea to
4e6d39f
Compare
|
🚫 Unpublished versions:
|
|
🚫 Unpublished versions:
|
4e6d39f to
3b20947
Compare
|
🚫 Unpublished versions:
|
3b20947 to
1585a93
Compare
|
🚫 Unpublished versions:
|
- add a unique execution uuid to the executionTrace - add the possibility to update executionTrace with a custom data - add the possibility to update the context of the instantiated class with the trace (if the contextKey is specified) - update tabkram.github.io/execution-engine documentation ✅ Compatibility Notice: - `metadata` are not handled in the engine ExecutionTrace for now, to avoid modifying the engine.
1585a93 to
5461699
Compare
|
🚫 Unpublished versions:
|
⚠️ Deprecation Notice: - `EdgeData` is deprecated, use `EngineEdgeData` instead. - `NodeTrace` is deprecated, use `EngineNodeTrace` instead. - `NodeData` is deprecated, use `EngineNodeData` instead. - `Node` is deprecated, use `EngineNode` instead. - `Edge` is deprecated, use `EngineEdge` instead. - `Trace` is deprecated, use `EngineTrace` instead. - `isNodeTrace` is deprecated, use `isEngineNodeTrace` instead.
|
🚫 Unpublished versions:
|
…ial` transformer to maintain compatibility after adding mandatory `id: string` in `ExecutionTrace` model. This prevents the TS2769: No overload matches this call error when executing `.run()` with a `narratives` transformer in `options?: TraceOptions<Array<any>, O>`
|
🚫 Unpublished versions:
|
|
🚫 Unpublished versions: |
create a generic
execute()function that handles async , async and hidden promises functioncreate standalone
executionTrace()function usage without requiring engine instantiation.introduce the
@trace()decorator to manageExecutionTrace, append functionmetadata, and enrich the boundcontextwith custom info.refactor trace and engine models.
rename
TraceableExecutiontoTraceableEngineto separate engine scope from standalone scoperefactor
TraceableEngineto use the commonexecutionTrace()function and theexecute()behinddoc and generate examples to ensure deprecated engin still work and supported
✅ Compatibility Notice: