Releases: stackables/bridge
@stackables/bridge@2.3.1
Patch Changes
-
#118
d6907a2Thanks @aarne! - Bridge Trace IDs - The engine now returns a compact Trace ID alongside your data (e.g., 0x2a). This ID can be decoded into an exact execution map showing precisely which wires, fallbacks, and conditions activated. Because every bridge has a finite number of execution paths, these IDs are perfect for zero-PII monitoring and bucketing telemetry data. -
Updated dependencies [
d6907a2]:- @stackables/bridge-core@1.6.1
- @stackables/bridge-graphql@1.2.2
- @stackables/bridge-parser@1.4.2
@stackables/bridge-parser@1.4.2
Patch Changes
- Updated dependencies [
d6907a2]:- @stackables/bridge-core@1.6.1
@stackables/bridge-graphql@1.2.2
Patch Changes
- Updated dependencies [
d6907a2]:- @stackables/bridge-core@1.6.1
@stackables/bridge-core@1.6.1
Patch Changes
- #118
d6907a2Thanks @aarne! - Bridge Trace IDs - The engine now returns a compact Trace ID alongside your data (e.g., 0x2a). This ID can be decoded into an exact execution map showing precisely which wires, fallbacks, and conditions activated. Because every bridge has a finite number of execution paths, these IDs are perfect for zero-PII monitoring and bucketing telemetry data.
@stackables/bridge-compiler@2.4.2
Patch Changes
- Updated dependencies [
d6907a2]:- @stackables/bridge-core@1.6.1
@stackables/bridge@2.3.0
Minor Changes
-
#112
375e2b0Thanks @aarne! - Improve native batched tool authoring by documenting the feature, exporting dedicated batch tool types, and simplifying the batch contract to plain input arrays.Batch tools now receive
Input[]and must returnOutput[]in matching order. Batched tool tracing and logging are also emitted once per flushed batch call instead of once per queued item.Native batching now works in compiled execution as well as the runtime interpreter. Batch tools can also signal partial failures by returning an
Errorat a specific result index, which rejects only that item and allows normal wire-levelcatchfallbacks to handle it.
Patch Changes
-
#108
de20eceThanks @aarne! - Add memoized tool handles with compiler support.Bridge
withdeclarations now supportmemoizefor tool handles, including
loop-scoped tool handles inside array mappings. Memoized handles reuse the same
result for repeated calls with identical inputs, and each declared handle keeps
its own cache.The AOT compiler now compiles memoized tool handles too, including loop-scoped
tool handles inside array mappings. Compiled execution preserves request-scoped
caching semantics and reuses results for repeated calls with identical inputs. -
#111
fc836e4Thanks @aarne! - Move Bridge source metadata onto BridgeDocument.Parsed documents now retain their original source text automatically, and can
optionally carry a filename from parse time. Runtime execution, compiler
fallbacks, GraphQL execution, and playground formatting now read that metadata
from the document instead of requiring callers to thread source and filename
through execute options. -
#111
fc836e4Thanks @aarne! - Improve formatted runtime errors for missing tools and source underlines.No tool found for "..."and missing registered tool-function errors now carry
Bridge source locations when they originate from authored bridge wires, so
formatted errors include the filename, line, and highlighted source span.
Control-flow throw fallbacks now preserve their own source span, so
?? throw "..."highlights only the throw clause instead of the whole wire.
Caret underlines now render the full inclusive source span instead of stopping
one character short. -
#111
fc836e4Thanks @aarne! - Fix segment-local?.traversal so later strict path segments still fail after a guarded null hop, and preserve source formatting forpaniccontrol-flow errors. -
#108
de20eceThanks @aarne! - Fix strict nested scope resolution for array mappings.Nested scopes can now read iterator aliases from visible parent scopes while
still resolving overlapping names to the nearest inner scope. This also keeps
invalid nested tool input wiring rejected during parsing. -
#111
fc836e4Thanks @aarne! - Improve runtime error source mapping for ternary conditions and strict path traversal.Runtime and compiled execution now preserve clause-level source spans for ternary conditions and branches, so formatted errors can highlight only the failing condition or selected branch instead of the whole wire.
Strict path traversal also now fails consistently on primitive property access in both runtime and AOT execution, keeping error messages and behavior aligned. -
Updated dependencies [
de20ece,fc836e4,375e2b0,fc836e4,fc836e4,de20ece,fc836e4]:- @stackables/bridge-core@1.6.0
- @stackables/bridge-parser@1.4.1
- @stackables/bridge-graphql@1.2.1
- @stackables/bridge-stdlib@1.5.3
@stackables/bridge-types@1.2.0
Minor Changes
-
#112
375e2b0Thanks @aarne! - Improve native batched tool authoring by documenting the feature, exporting dedicated batch tool types, and simplifying the batch contract to plain input arrays.Batch tools now receive
Input[]and must returnOutput[]in matching order. Batched tool tracing and logging are also emitted once per flushed batch call instead of once per queued item.Native batching now works in compiled execution as well as the runtime interpreter. Batch tools can also signal partial failures by returning an
Errorat a specific result index, which rejects only that item and allows normal wire-levelcatchfallbacks to handle it.
@stackables/bridge-stdlib@1.5.3
Patch Changes
- Updated dependencies [
375e2b0]:- @stackables/bridge-types@1.2.0
@stackables/bridge-parser@1.4.1
Patch Changes
-
#108
de20eceThanks @aarne! - Add memoized tool handles with compiler support.Bridge
withdeclarations now supportmemoizefor tool handles, including
loop-scoped tool handles inside array mappings. Memoized handles reuse the same
result for repeated calls with identical inputs, and each declared handle keeps
its own cache.The AOT compiler now compiles memoized tool handles too, including loop-scoped
tool handles inside array mappings. Compiled execution preserves request-scoped
caching semantics and reuses results for repeated calls with identical inputs. -
#111
fc836e4Thanks @aarne! - Move Bridge source metadata onto BridgeDocument.Parsed documents now retain their original source text automatically, and can
optionally carry a filename from parse time. Runtime execution, compiler
fallbacks, GraphQL execution, and playground formatting now read that metadata
from the document instead of requiring callers to thread source and filename
through execute options. -
#108
de20eceThanks @aarne! - Fix strict nested scope resolution for array mappings.Nested scopes can now read iterator aliases from visible parent scopes while
still resolving overlapping names to the nearest inner scope. This also keeps
invalid nested tool input wiring rejected during parsing. -
#111
fc836e4Thanks @aarne! - Improve runtime error source mapping for ternary conditions and strict path traversal.Runtime and compiled execution now preserve clause-level source spans for ternary conditions and branches, so formatted errors can highlight only the failing condition or selected branch instead of the whole wire.
Strict path traversal also now fails consistently on primitive property access in both runtime and AOT execution, keeping error messages and behavior aligned. -
Updated dependencies [
de20ece,fc836e4,375e2b0,fc836e4,fc836e4,de20ece,fc836e4]:- @stackables/bridge-core@1.6.0
- @stackables/bridge-stdlib@1.5.3
@stackables/bridge-graphql@1.2.1
Patch Changes
-
#111
fc836e4Thanks @aarne! - Move Bridge source metadata onto BridgeDocument.Parsed documents now retain their original source text automatically, and can
optionally carry a filename from parse time. Runtime execution, compiler
fallbacks, GraphQL execution, and playground formatting now read that metadata
from the document instead of requiring callers to thread source and filename
through execute options. -
Updated dependencies [
de20ece,fc836e4,375e2b0,fc836e4,fc836e4,de20ece,fc836e4]:- @stackables/bridge-core@1.6.0
- @stackables/bridge-stdlib@1.5.3