Chore v1.3.5

Hi, thank you for making this project. There is a problem with button in primaryAction (as far as I tried). When it is disabled by initial and then transition to enabled state, clicking on it does not do anything. Could you investigate and it?

Fix: add generate key method for reloading button component on loading | disable

Merge pull request #185 from ownego/180-button-not-working-when-the-state-is-disabled-then-transition-to-enabled

Fix: add generate key method for reloading button component on loading | disabled

• Cause: loading and disabled props only change button styles -> button won't update

• Solution: add generate key method for updating component everytime disabled|loading props change

• Test with page actions component

• Test with normal button component

• Test with build command

Hi, thanks for this library!

I'm trying to render some content in a Frame. I see some components use <script setup>, but not this one: https://ownego.github.io/polaris-vue/?path=/docs/components-frame--frame

Would it be possible to update it to use <script setup> too?

Thanks!

PS: Is there a hello world full app example?

Update: biweekly option

Merge remote-tracking branch 'origin/main' into oe-version

Update: biweekly option

Update: biweekly option

The Frame docs have a screenshot with a full-screen app. For me, app using Frame still shows the Shopify sidebar. Is it actually possible to hide Shopify sidebar and leave more screen for the app?

Found the same question here: https://community.shopify.com/c/shopify-apis-and-sdks/hiding-shopify-ui-elements-in-an-embedded-app/td-p/1250926

Thanks

@mariusa Seem likes you do not fully understand the embedded app from Shopify... I think you should read the Shopify document first. There is a way to do fullscreen app mode for embedded app is using appBridge full screen method. Otherwise, if you want your app to be fullscreen, you have to build the un-embedded app (an separated app system)

I'm closing this question here. You should read the documentation and understand Shopify system first.

@mariusa Of course you are, the script setup does not related to the component itself, you can use composition API or options API, it's up to you.

I don't have an full app example but I'm using the library for all of my apps, and I see it works well. I will update or fix bug if there is something wrong.

@mariusa the answer is Yes, you don't have to do anything, just do not use the #navigation slot, then the screen will be full.

Actually, I'm also using the Frame without navigation for my apps.

WIP: calloutCard

Chore v1.3.4

Hotfix: update Link component not work with vue-router

Update: add vue-router for development stage to work with vue-router

Update: update docs for Link component

Update: modify comments in main.ts file

Merge pull request #181 from ownego/hotfix/link-component-not-work-with-vue-router

Hotfix/link component not work with vue router

Tested with vue-router Tested with normal link Tested with build command

Ok so there are 2 issues (1 critical) with the private apps in 6.0.0

1. There is no navigation item to navigate to private apps page if you're free workspace. I have to access via finding the url in browser history.
2. When I tried to save the settings of an private app, there is a critical issue when the server's CPU gonna 100%, and the workspace crashed. Anytime I go to marketplace or private app page, the CPU is running high, and after settings, it's crashed. And beside that, after save the settings, the settings page is also gone...

Description:

I see RC move the marketplace and public apps as enterprise feature. But we're using RC for years, and have some privated apps that have been developed by us or we hired some freelancers to built, but now I see we cannot access those apps.

I think that's not fair, I agree with the marketplace as enterprise feature, but with privated apps, that does not make sense. I hope RC should consider and bring it back soon.

@tuanpham-dev Hey there, what component are you talking about?

@davykiash Actually, I've already been developing Vue 3 version in the next branch, but currently it's just a scaffolding. I will try to keep going but I think it can't be soon because I have less time at this moment.