Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,7 @@ jobs:
run: |
npm ci
npm run typecheck
npm test
npm run build

- name: Verify generated client assets
Expand Down
2 changes: 2 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,8 @@ for versioning and publishing steps.
```powershell
cd src/XperienceCommunity.FormsToolkit/Client
npm ci
npm run typecheck
npm test
npm run build
```

Expand Down
10 changes: 10 additions & 0 deletions docs/Contributing-Setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,9 +72,19 @@ When changing files under `src/XperienceCommunity.FormsToolkit/Client/src`, run:
```powershell
cd src/XperienceCommunity.FormsToolkit/Client
npm ci
npm run typecheck
npm test
npm run build
```

`npm test` runs the component tests (`*.test.tsx` next to each component) with
Vitest and React Testing Library. The Kentico admin packages only run inside the
Xperience administration, so the tests replace them with the test doubles in
`Client/test/kentico`: `usePageCommand` returns responses set with
`mockPageCommand` and records every payload in `pageCommandCalls`, and the admin
components render plain, labelled HTML. When a component starts using another
admin export, add a stand-in for it there.

Commit the generated `Client/dist` assets with the source changes. Normal package
consumers do not need Node.js because the built administration module is embedded
in the Forms Toolkit assembly.
Expand Down
Loading
Loading