Skip to content

Conversation

teallarson
Copy link
Collaborator

No description provided.

@teallarson teallarson requested a review from girarda May 8, 2025 14:49
import { EmbeddedWidget } from "https://cdn.jsdelivr.net/npm/@airbyte-embedded/[email protected]/+esm";

window.addEventListener("load", async () => {
<script src="https://cdn.jsdelivr.net/npm/@airbyte-embedded/airbyte-embedded-widget"></script>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice. this will always use the latest version, right?

Copy link
Collaborator Author

@teallarson teallarson May 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it will. It's honestly much better for an Operator to pin a specific version (since version changes could break their implementation). This is low maintenance for us, but not an example of a best practice... I actually had a commit locally to pin the version 😅. Lmk what you think.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And FWIW our release cadence is pretty likely to slow down here I would imagine. Most of the changes are in the webapp and server, not in the widget itself.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree it's not best practice, but I think the demo should use the latest just to keep the maintenance low. We can tell them to pin in it in the setup instructions

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can revisit when there’s fewer releases

@teallarson teallarson merged commit acbc8a0 into main May 8, 2025
@teallarson teallarson deleted the teal/update-demo-and-exports branch May 8, 2025 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants