Skip to main content

Feature Requests

If something you want isn't covered in these docs, the way to ask for it is a GitHub issue — not a public roadmap doc.

Where to file one​

File against get-enlace/enlace regardless of which adapter you're using — it's where the canvas, execution engine, and credential handling actually live. The one exception is a request specific to how an adapter itself behaves (e.g. spec auto-detection in ASP.NET Core) — file those against that adapter's own repo instead (enlace-js or enlace-dotnet).

Open a new issue on enlace →

Known gaps​

A few things Enlace doesn't do today, so you don't need to file these — just 👍 or comment on the existing conversation:

  • Multiple saved local workflows. This browser's own autosave keeps exactly one slot — loading a different workflow overwrites it. Export a .enlace file if you want to keep more than one around.
  • Drag-connect between fields on the canvas. Field mapping goes through typing {{ in the field itself and picking a source in the menu that opens — not a direct drag between two fields.
  • Full OAuth2 authorization_code support. Only the Cookie credential's session-cookie flow exists; Enlace doesn't yet capture a token from a login redirect.

What's helpful to include​

  • The problem, not just the solution — what are you trying to build a chain around that Enlace can't do today?
  • A sample spec or operation shape, if the request is about how a particular OpenAPI construct should render.

Found something that looks broken rather than missing? Same repo, same tracker — just describe what you expected vs. what happened.