Skip to content

Releases: tabkram/execution-engine

v4.0.0

Choose a tag to compare

@tabkram tabkram released this 08 Aug 16:09

What's Changed

  • feat: make context injection into functions optional when we trace by @tabkram in #71

Full Changelog: v3.5.0...v4.0.0

v3.5.0

Choose a tag to compare

@tabkram tabkram released this 10 Apr 18:42

What's Changed

  • feat: add bypass argument to cache options by @tabkram in #70

Full Changelog: v3.4.0...v3.5.0

v3.4.0

Choose a tag to compare

@tabkram tabkram released this 30 Mar 15:32

What's Changed

  • feat: add @cache decorator with configurable options (cacheManager, cacheKey, etc.) by @tabkram in #65
  • docs: update doc and usage examples for @memoize, @cache and @trace decorators by @tabkram in #66
  • refactor(execution): memoize options by @tabkram in #67
  • refactor(execution): trace options by @tabkram in #68
  • refactor(execution): trace options by @tabkram in #69

Full Changelog: v3.3.1...v3.4.0

v3.3.1

Choose a tag to compare

@tabkram tabkram released this 21 Mar 02:27

What's Changed

  • fix(memoize): correctly throw error on memoize when the original method throws by @tabkram in #64

Full Changelog: v3.3.0...v3.3.1

v3.3.0

Choose a tag to compare

@tabkram tabkram released this 10 Mar 10:21

What's Changed

  • feat: introduce the @memoize decorator for method memoization, caching results to avoid redundant calculations by @tabkram in #63

Full Changelog: v3.2.0...v3.3.0

v3.2.0

Choose a tag to compare

@tabkram tabkram released this 08 Mar 12:24

What's Changed

  • uuidv4 dependency replaced with crypto.randomUUID by @tabkram in #60
  • completed ts-doc for models by @tabkram in #62

Full Changelog: v3.1.1...v3.2.0

v3.1.1

Choose a tag to compare

@tabkram tabkram released this 03 Mar 07:33

What's Changed

  • fix: @trace() execution to correctly auto bind the class context to the handler by @tabkram in #58
  • fix: improve @trace execution to correctly auto bind the class context to the handler by @tabkram in #59

Full Changelog: v3.1.0...v3.1.1

v3.1.0

Choose a tag to compare

@tabkram tabkram released this 25 Feb 23:01

What's Changed

  • fix(execution): multi-decorator support with @trace() and handle hidden returned promises by @tabkram in #57

Compatibility Notice

  • The execute() function now passes two arguments to the callback instead of one.
  • The execute() function no longer includes the options argument and does not update the context when bound.
  • Except for these minor changes, this PR maintains full backward compatibility (NO BREAKING CHANGES) ✅.

Full Changelog: v3.0.0...v3.1.0

v3.0.0

Choose a tag to compare

@tabkram tabkram released this 24 Feb 19:51

What's Changed

  • feat: add standalone executionTrace() for use without engine instantiation by @tabkram in #54
  • feat: introduce @trace() decorator to manage ExecutionTrace, append metadata, and enrich context by @tabkram in #54
  • refactor: rename models and separate engine from execution layer by @tabkram in #54

Full Changelog: v2.2.3...v3.0.0

✅ Compatibility Notice

  • This release maintains full backward compatibility (NO BREAKING CHANGES) ✅
  • Users can continue using deprecated models until they're ready to migrate.

⚠️ Deprecation Notice:

  • NodeExecutionTrace is deprecated, Use ExecutionTrace instead.
  • NodeExecutionTraceExtractor is deprecated. Use ExecutionTraceExtractor instead.
  • isNodeExecutionTrace is deprecated. Use isExecutionTrace instead.
  • TraceableExecution is deprecated and will be removed in a future release. Use TraceableEngine instead.
  • 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.

v2.2.3

Choose a tag to compare

@tabkram tabkram released this 20 Feb 23:40

What's Changed

  • feat: ensure trace errors are safe, avoid circular references and serialization issues by @tabkram in #53

Full Changelog: v2.2.2...v2.2.3