Maciek Kucmus
Maciek Kucmus
### Description There should be a place to allow to an user to unsubscribe provided email from newsletter. ### Acceptance criteria - [ ] there is a dedicated page for...
### Description Seo meta-data is not available in `useCms` composable for pages in type "langing page". From short investigation, the data is not presented in the response from API so...
### What happened? Sometimes there is little lag between when loading a cart information. Once the cart is cleared, on new page view there is still an old cart available...
### Description Currently, the [useWishlist](https://github.com/vuestorefront/shopware-pwa/blob/master/packages/composables/src/logic/useWishlist.ts) composable utilizes only a local storage to keep information in the browser on what products are in. Since some time, the API enables the wishlist...
### Description Currently, the internal theme's [usePriceFilter](https://github.com/vuestorefront/shopware-pwa/blob/master/packages/default-theme/src/logic/usePriceFilter.js) composable is not typed at all. ### Acceptance criteria - [ ] usePriceFilter has its representive in TypeScript
### Description  According to the swagger documentation, many of endpoints accepts the same set of common parameters, under the name "Criteria". In Shopware PWA interfaces it's equivalent of [ShopwareSearchParams](https://github.com/vuestorefront/shopware-pwa/blob/master/packages/commons/interfaces/search/SearchCriteria.ts#L55)....
### Description ### Acceptance criteria - [ ] displayState computed is refactored in order to get the `displayStateInRegistration` once it's available in SW6 configuration
### What happened? So far, `route` property isn't refreshed every time it needs to be. Noticed in `notifications.js` plugin in default theme; route property used in interceptor handler isn't up...
### Description build and document types included in @shopware-pwa/commons package  ### Acceptance criteria - [ ]
## Changes provides a workaround to not use page resolver from SwagShopwarePwa plugin: - use `/seo-url` endpoint to resolve the URL - fetch the corresponding entity using dedicated endpoint: product,...