Web components breaking changes - versioning?

Polaris
1

Hey all,

I’m using web components in production and I’m wondering if there’s a way to lock the script to a specific version?

I know it’s experimental and you’re chaning things, but a recent change has caused all labels on s-choice elements to be invisible.

Syntax before:
<s-choice label="Hidden" value="hidden"></s-choice>

Syntax now:
<s-choice value="hidden">Hidden</s-choice>

So all previous choice that have empty tags (no text between opening and closing tag) now don’t display anything.

This is of course causing confusion for the merchants.

Any chance we can lock the version of the “app-bridge-ui-experimental.js”?
Or should I just save it locally and use that?

Thanks,
Peter

2

Hey Peter, sorry for the confusion here. This was an intentional breaking change and in the future we will have backwards compatibility for changes like this i.e. no breaking changes at all.

I would also add, please make sure you’re not using these components in merchant facing apps until we’ve released these components to general audience.

Thanks,

Kyle

3

Thanks @Kyle_Durand !

Any ETA for the release of web components?

I love them - I don’t like using React, just want to use the minimum vanilla JS, and the new web components are so much nicer to use than old polaris classes.

Great job!

4

Thank you! No ETA at the moment but we’re working really hard

5

This is actually an issue in the documentation EmptyState. The version it uses has a broken implementation of the s-button-group , if you use the example code with <"script src=“https://cdn.shopify.com/shopifycloud/polaris.js”> like the documentation says to it has the same behavior. If you remove the button group or use the experimental script it works correctly.

image
image508×830 106 KB