Skip to content

Commit 434592d

Browse files
committed
Merge branch 'docs/multibrand' of https://github.com/vuestorefront/vue-storefront into docs/multibrand
2 parents b2125f8 + c4ef339 commit 434592d

File tree

2 files changed

+10
-9
lines changed

2 files changed

+10
-9
lines changed

docs/content/guides/7.multistore/2.tooling-and-concepts/2.development/4.local-environment.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The most common way to start development is using the yarn scripts from the root
3434
yarn dev
3535

3636
# Start development for a specific store
37-
yarn store dev --store-id=my-store
37+
yarn store dev --store-id=my-store
3838
# Alternatively, you may use: ./node_modules/.bin/alokai-cli store dev --store-id=my-store
3939
```
4040

@@ -86,7 +86,7 @@ yarn store dev --all --with-local-domains
8686
```
8787

8888
:::tip HTTPS
89-
Caddy automatically generates self-signed SSL certificates for local domains. You
89+
Caddy automatically generates self-signed SSL certificates for local domains. You
9090
can read more about it in the [Caddy documentation](https://caddyserver.com/docs/automatic-https).
9191
:::
9292

@@ -117,7 +117,7 @@ yarn test:integration:pw
117117
You can also run tests in Playwright's UI mode for better debugging experience:
118118

119119
```bash
120-
yarn store test --store-id=my-store --ui
120+
yarn store test --store-id=my-store --ui
121121
```
122122

123123
:::warning
@@ -195,6 +195,7 @@ This will skip the build and only compose the store into the `.out` directory.
195195
#description
196196
Learn how to create and run integration tests using Playwright in your Alokai multistore project.
197197

198+
198199
#cta
199200
:::docs-arrow-link{to="/guides/multistore/tooling-and-concepts/integration-tests"}
200201
Next

docs/content/guides/7.multistore/2.tooling-and-concepts/2.development/5.integration-tests.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Here's our project structure:
3737
apps/
3838
├── storefront-unified-nextjs/ # Base shared code
3939
└── stores/
40-
├── fashion-brand/
40+
├── fashion-brand/
4141
│ ├── playwright/
4242
│ ├── storefront-middleware/ # Middleware customizations
4343
│ │ └── integrations/
@@ -122,13 +122,13 @@ import { serverFactory as recommendationsEndpoints } from './recommendations/ser
122122

123123
export const mainRouterFactory = () => {
124124
const mainRouter = createRouter();
125-
125+
126126
// ... existing router setup ...
127127

128128
// Add your new mock router
129129
const recommendationsRouter = pipe(recommendationsEndpoints, createRouter());
130130
mainRouter.use(
131-
'/commerce/recommendations/**',
131+
'/commerce/recommendations/**',
132132
useBase('/commerce/recommendations', recommendationsRouter.handler)
133133
);
134134

@@ -228,7 +228,7 @@ test.describe('Recommendations page', () => {
228228

229229
// Verify recommendations are visible
230230
await expect(recommendationsPage.recommendationsGrid).toBeVisible();
231-
231+
232232
// Add more assertions as needed
233233
});
234234
});
@@ -255,7 +255,7 @@ yarn store test --store-id=fashion-brand --ui
255255
UI mode is great for debugging as it shows test execution step by step and lets you inspect the page state.
256256
::
257257

258-
![Playwright UI](/guides/multistore/img/running-test-in-ui-mode.png)
258+
![Playwright UI](/guides/7.multistore/img/running-test-in-ui-mode.png)
259259

260260
::
261261

@@ -274,4 +274,4 @@ Learn how Alokai handles store deployment and what happens behind the scenes.
274274
:::docs-arrow-link{to="/guides/multistore/tooling-and-concepts/deployment"}
275275
Next
276276
:::
277-
::
277+
::

0 commit comments

Comments
 (0)