All issues

Document migration path from v1 channels to typed streams#47

New issue
Open
LNLNcommented 6d ago

Is your feature request related to a problem?

Document migration path from v1 channels to typed streams — today the workflow on wavelet requires an out-of-band step that breaks the editor flow and makes the API harder to type.

Describe the solution you'd like

Migrate the affected surface to follow the same contract as the rest of the toolchain, so composed flows stay consistent and predictable.

Describe alternatives you've considered

  • Keep the current implementation and document the seam.
  • Ship a codemod that rewrites call sites at install time.

However, both would still leave the surface on a different contract from the rest of the stack, and would only delay the cleanup.

Labels: documentation, good first issue

LNLNcommented 6d ago

Could we add a regression test before the patch lands? Otherwise this will resurface as soon as the surrounding cleanup happens.

LNLNcommented 6d ago

Bumping priority — three customers hit this last week, two of them on the enterprise tier.

LNln-dev7self-assigned this6d ago
LNln-dev7added the labeldocumentation6d ago
LNLNcommented 6d ago

Re-reading the spec, I think the right contract is the one in the bug report, not the one we're shipping. Going to open a small PR.

LNln-dev7added a commit that references this issuefix(wavelet): wire the new contract for #4703085615d ago
LNln-dev7mentioned this in#985d ago

Add a comment

M↓Markdown is supported