async-fp

Major Changes

• d0a68ba: Initial release.

  In this release, the basic functionality are working,
  except that dynamic dependencies are treated as static dependencies.

  This means the required dynamic dependencies need to be provided before adding the dependent gizmo.

Major Changes

• d0a68ba: Release as Node ESM module

Minor Changes

• d0a68ba: Add @unional/gizmo

Patch Changes

• Updated dependencies [d0a68ba]
• Updated dependencies [d0a68ba]
  • @unional/[email protected]
  • @unional/[email protected]

Patch Changes

• f6ee884: Fix support of async asserter
• Updated dependencies [41af4c1]
  • @unional/[email protected]

Patch Changes

• 41af4c1: Adjust import type syntax

Minor Changes

• dfdb419: Add asyncAssert().

Patch Changes

• @unional/[email protected]

Patch Changes

• 593f104: Update type-plus

Patch Changes

• Updated dependencies [593f104]
  • @unional/[email protected]

Patch Changes

• Updated dependencies [5ac78c2]
  • @unional/[email protected]

Patch Changes

• 5ac78c2: Fix extend() to work with union types.

  The problem is this type:

  extend(context: AsyncContext.Transformer<CurrentContext, AdditionalContext>)
  

  The CurrentContext here overrides the generic resolution,
  making the CurrentContext becomes whatever the transformer request,
  instead of the real current context.

Patch Changes

• 51517d9: Fix workspace:* -> workspace:^ reference
• Updated dependencies [9c1ecfb]
  • @unional/[email protected]

Patch Changes

• 9c1ecfb: Update type-plus and iso-error

Major Changes

• 189343b: Restore the extend() behavior in 2.0,
  that it returns a new instance instead of itself.

  The clone() function is also removed as it is not necessary anymore.

  The behavior introduced in 3.0 makes the async context mutable.
  Which clone() was added to mitigate that.

  However, such design is architecturally unsound.

  With this change, make sure you are updating or assigning the new instance after extend():

  // from
  const ctx = new AsyncContext()
  
  ctx.extend(...)
  
  // to
  const ctx = new AsyncContext()
  
  const extended = ctx.extend(...)
  

Major Changes

• 189343b: Restore the extend() behavior in 2.0,
  that it returns a new instance instead of itself.

  The clone() function is also removed as it is not necessary anymore.

  The behavior introduced in 3.0 makes the async context mutable.
  Which clone() was added to mitigate that.

  However, such design is architecturally unsound.

  With this change, make sure you are updating or assigning the new instance after extend():

  // from
  const ctx = new AsyncContext()
  
  ctx.extend(...)
  
  // to
  const ctx = new AsyncContext()
  
  const extended = ctx.extend(...)
  

Patch Changes

• Updated dependencies [189343b]
  • @unional/[email protected]

Patch Changes

• Updated dependencies [66b9fc8]
  • @unional/[email protected]

Minor Changes

• 66b9fc8: Detect blocking get calls

Patch Changes

• 1091796: Supports calling extend() after get().

  This was supported in 2.0 implicitly because each extend() creates a new context.

  This is useful when different code using the context calls get() and extend() at their own rate.

  The new extend() will not affect the existing get() result, which is expected.
  If not, it will be very hard to reason and debug.

Patch Changes

• Updated dependencies [1091796]
  • @unional/[email protected]

Patch Changes

• Updated dependencies [0e14e94]
  • @unional/[email protected]

Minor Changes

• 0e14e94: Add clone() to create a new context out of the original one.

  Changing the extend() function to return itself while keeping the name is an oversight in 3.0.
  The naming is a bit confusing.

  It will be renamed in 4.0.