rjsf-testing
Skill16k starsChanged 20 days agoApache-2.0View on GitHub
Use when writing, modifying, converting, or debugging any test in this repo, including a regression test added during a bug fix — test helpers, user-event vs fireEvent rules, fake timers, and snapshot updates.
Trending
More talk lately.about the whole repository
Who's talking about rjsf-team/react-jsonschema-form
- argoproj/argo-cd“Use a form generator for parameters if json schema is provided”GitHub · Apr 22, 2021 · 9 reactions
- mui/toolpad“Add support for JSON form”GitHub · Oct 24, 2023 · 7 reactions
- vitejs/vite“Issue with tree-shaking in Vite 8.1.0 / rolldown >= 1.1.0 with complex module graph”GitHub · Jun 26, 2026 · 6 reactions
- Stack Overflow“how can i use react form builder 2 in react js project”Stack Overflow · Oct 28, 2020 · 4 votes
- mokkabonna/json-schema-compare“Package does not get transpiled when used with webpack/babel”GitHub · May 29, 2020 · 4 reactions
The biggest 5 of 64 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 64
Talked about on GitHub, Stack Overflow, Hacker News and Bluesky (64 times).
On GitHub · 50
- Apr 22, 2021Use a form generator for parameters if json schema is provided — argoproj/argo-cd9 reactions
- Oct 24, 2023Add support for JSON form — mui/toolpad7 reactions · 2 comments
- Jun 26, 2026Issue with tree-shaking in Vite 8.1.0 / rolldown >= 1.1.0 with complex module graph — vitejs/vite6 reactions · 5 comments
- May 29, 2020Package does not get transpiled when used with webpack/babel — mokkabonna/json-schema-compare4 reactions
- Apr 10, 2026fix: add guard to handle null values in getRealHeight — ant-design/ant-design2 reactions · 7 comments
45 more on GitHub
- Oct 9, 2025[ENHANCEMENT]: Add input / output schemas & auto generated forms to datasets — Arize-ai/phoenix2 reactions · 3 comments
- May 14, 2020PyCon Mentored Sprints meta-issue — HypothesisWorks/hypothesis2 reactions · 21 comments
- Aug 18, 2026Pin RJSF Core to 6.7.0 and add comma-decimal E2E tests — Lundalogik/lime-elements1 reaction · 6 comments
- Jul 15, 2025Feature request: Custom Properties in Custom Widgets — gristlabs/grist-core1 reaction · 2 comments
- Dec 22, 2024[FEATURE-REQUEST] Use selectors in the configuration — Luligu/matterbridge-shelly1 reaction · 32 comments
- Nov 12, 2024Update @rjsf/* to 5.22.4 — bratislava/konto.bratislava.sk1 reaction · 1 comment
- Sep 25, 2024front: bump the all group across 1 directory with 102 updates — OpenRailAssociation/osrd1 reaction · 1 comment
- Aug 25, 2023🐛 Bug Report: Unexpected form behaviour when using custom field extension for dynamic fields — backstage/backstage1 reaction · 10 comments
- Jun 11, 2023[BUDI-7428] Dynamic form based on JSON Schema — Budibase/budibase1 reaction · 3 comments
- Feb 1, 2023Display validation errors in JSON schema form on change/blur of form fields — giantswarm/happa1 reaction · 3 comments
- Feb 1, 2023duplicate of https://github.com/rjsf-team/react-jsonschema-form — rhysv96/json-gui1 reaction
- Jun 23, 2021A story for hiding the submit button — commitd/components-rjsf1 reaction
- Dec 2, 2020Bug 1901531: Fix runtime error in create CR form — openshift/console1 reaction · 3 comments
- Sep 7, 2020Support advanced forms from json schema — holoviz/panel1 reaction · 2 comments
- May 9, 2020Consider to generalize building admin ui forms with jsonschema — birkir/prime1 reaction
- Apr 21, 2020Custom fields in schema forms — Lundalogik/lime-elements1 reaction · 4 comments
- Sep 10, 2019[@types/react-jsonschema-form] failed to import SchemaField — DefinitelyTyped/DefinitelyTyped1 reaction · 2 comments
- Nov 13, 2026Bump the rjsf group in /springdoc-openapi-starter-common-mcp/src/main/frontend with 3 updates — springdoc/springdoc-openapi0 reactions
- Oct 28, 2026Bump @rjsf/core from 5.24.1 to 6.11.0 in /superset-frontend — gnanaprakashn/supser-docker0 reactions · 1 comment
- Oct 26, 2026build(deps-dev): bump @rjsf/core from 5.24.13 to 6.11.0 in /spikes/backstage-adoption — texaryn/texaryn0 reactions
- Oct 20, 2026[build] release — x0k/svelte-jsonschema-form0 reactions
- Oct 19, 2026Bump @rjsf/validator-ajv8 from 6.4.1 to 6.11.0 in /web — Omnisystechnology/traffic0 reactions
- Oct 6, 2026chore(deps): bump the rjsf group in /superset-frontend with 3 updates — EZE-YoBoi/ovyero-rt-sam-17910778670 reactions
- Sep 26, 2026Bump @rjsf/validator-ajv8 from 5.24.12 to 6.10.1 in /superset-frontend — JJSolutions-lab/superset0 reactions · 1 comment
- Sep 24, 2026chore(deps): bump the rjsf group in /superset-frontend with 3 updates — danielsaisani/superset0 reactions · 1 comment
- Sep 23, 2026chore(deps): bump the rjsf group in /superset-frontend with 3 updates — zhaoyongjie/incubator-superset0 reactions · 2 comments
- Sep 23, 2026chore(deps): bump the rjsf group across 1 directory with 3 updates — jpribeiro1987/bi_superset0 reactions · 1 comment
- Sep 17, 2026chore(deps): bump the rjsf group in /superset-frontend with 3 updates — codev-workshops/bhaskar887-superset0 reactions · 1 comment
- Sep 13, 2026Bump @rjsf/validator-ajv8 from 5.23.2 to 6.10.0 in /frontend — meridian-analytics/maipl0 reactions
- Sep 8, 2026chore(deps): bump @rjsf/core from 5.24.13 to 6.8.0 in /superset-frontend — tungsfer512/superset0 reactions · 1 comment
- Sep 8, 2026chore(deps): bump @rjsf/validator-ajv8 from 5.24.13 to 6.8.0 in /superset-frontend — tungsfer512/superset0 reactions · 1 comment
- Sep 8, 2026Bump the rjsf group in /superset-frontend with 3 updates — gurusevak-debug/super-set0 reactions · 1 comment
- Aug 24, 2026chore(deps): bump the rjsf group in /superset-frontend with 3 updates — nytai/superset0 reactions · 1 comment
- Aug 23, 2026chore(deps): bump the rjsf group across 1 directory with 3 updates — akhayyum22/superset0 reactions · 1 comment
- Aug 21, 2026chore(deps): bump the rjsf group in /superset-frontend with 3 updates — vaughnalec04-ui/demosuperset0 reactions · 1 comment
- Aug 21, 2026Bump the rjsf group across 1 directory with 3 updates — cuonvm-tlu/hust-pttk-capstone-project0 reactions · 1 comment
- Aug 13, 2026chore(deps-dev): bump @rjsf/utils from 6.6.2 to 6.7.1 — layer5io/sistent0 reactions
- Aug 13, 2026chore(deps-dev): bump @rjsf/core from 6.6.1 to 6.7.1 — layer5io/sistent0 reactions
- Aug 13, 2026build(deps): bump @rjsf/core from 5.24.13 to 6.8.0 in /superset-frontend — schahbod/SupersetPlugin0 reactions · 1 comment
- Aug 10, 2026chore(deps): bump @rjsf/validator-ajv8 from 5.24.2 to 6.7.1 — linode/apl-console0 reactions · 4 comments
- Aug 7, 2026Bump @rjsf/utils from 5.20.1 to 5.24.13 — usdoj/foia.gov0 reactions
- Jul 27, 2026chore(deps): bump the rjsf group in /superset-frontend with 3 updates — zimara-cloud/superset-stack0 reactions · 1 comment
- Jul 27, 2026chore(deps): bump the rjsf group in /superset-frontend with 3 updates — sakthisudarshan/superset0 reactions · 1 comment
- Jul 26, 2026chore(deps): bump the rjsf group across 1 directory with 3 updates — priyalwalpita/superset0 reactions · 1 comment
- Jun 2, 2026chore(deps): bump the rjsf group in /frontend with 3 updates — bolin8017/lolday0 reactions
On Stack Overflow · 12
- Oct 28, 2020how can i use react form builder 2 in react js project4 votes
- Jun 3, 2021How to invert dependencies in react-json-schema-form2 votes · 1 answer
- May 31, 2021how to build dynamic form builder with jquery2 votes
- Oct 28, 2023JSON Schema Form - min or max for date format1 vote
- Aug 7, 2023Best way to autogenerate React form from OpenAPI specification?1 vote
7 more on Stack Overflow
- Apr 12, 2022Error while using react-jsonschema-form with material in typescript project1 vote · 2 answers
- Oct 25, 2020Multi column support for react-jsonschema-form1 vote · 4 answers
- Oct 5, 2022react-jsonschema-form input box out of focus when ObjectFieldTemplate is used0 votes · 2 answers
- Aug 21, 2020react-jsonschema-form updown widget minimum registered but not enforced0 votes
- Jul 11, 2020How to display Form component in React app from react-jsonschema-form library? 'JSONSchemaForm' is not defined no-undef0 votes · 1 answer
- May 9, 2020Placement of conditional elements using JSON form schemas0 votes · 1 answer
- Sep 12, 2019Is it possible to define a jsonSchema for the jsonSchema specification?0 votes
On Hacker News · 1
- Oct 26, 2026A React component for building Web forms from JSON Schema2 points
On Bluesky · 1
- Nov 7, 2025#reactjs github.com/rjsf-team/re... — @lloveras.info2 likes and reposts
In this repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Run one package's tests with cd packages/<pkg> && pnpm test, or pnpm run test:watch there for watch mode.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Testing in react-jsonschema-form
- Vitest, jsdom and Testing Library; the shared config is
testing/vitest.base.ts, extended by each package's own vitest config - Run one package's tests with
cd packages/<pkg> && pnpm test, orpnpm run test:watchthere for watch mode; the rootpnpm testruns every package - Tests resolve
@rjsf/*imports to TypeScript source via the@rjsf/sourceexport condition, so no build is needed before running them - Vitest runs with
globals: true,testing/testSetup.tsloads@testing-library/jest-dom/vitest, andtsconfig.typecheck.json, which the tests are checked under (chakra-ui's throughtsconfig.typecheck-bundler.json, which extends it), listsvitest/globalsand@testing-library/jest-dom/vitestin itstypes, sodescribe,it,test,expect,expectTypeOf,vi, thebefore*/after*hooks and the jest-dom matchers are all ambient. Never import a runtime value from'vitest', in any form; only types, asimport type { Mock, MockInstance } from 'vitest'. Ano-restricted-importslint rule ontest/,packages/snapshot-tests/src/andtesting/fails on any other import from'vitest', aliased, namespace and default forms included - Build on the existing test helpers rather than hand-rolling the same setup.
packages/core/test/testUtils.tsxholds most of them and is the first place to look before writing scaffolding:createFormComponent(props)renders aFormwith the AJV 8 validator wired up and returns{ node, onChange, onSubmit, onError, rerender };createComponentdoes the same for a themedForm, andcreateFormRefcovers theFormRefcasessubmitForm(node, user)submits through the real submit button, falling back tofireEvent.submitwhen there isn't one. Its third argument,forceFireEvent, is the escape hatch for a test where clicking would focus the button and blur a focused field first, or where the browser's own constraint validation would block the submit the test means to make — pass it deliberately and say whyfieldErrorsById(node),errorListMessages(node)andexpectToHaveBeenCalledWithFormData(mock, formData)for assertions;getSelectedOptionValue(select)for a<select>'s rendered textsetupConsoleErrorSuppression()/setupConsoleWarnSuppression()for a test that intentionally triggers a console error, instead of an ad-hocvi.spyOn(console, ...). They live intesting/consoleSuppression.ts, whichtestUtils.tsxre-exports, so a theme package's tests import them from theredescribeRepeated(title, fn)runs a block against both the plain and theomitExtraDataform variants
- A theme package testing a widget or template directly (not through a
Form) builds its registry withgetTestRegistry()from@rjsf/core/testing, which takes optionalrootSchema,fields,templatesandwidgets. Pass the theme's ownTemplateswhen the assertion depends on the theme rendering — the default builds core's registry, so a test that omits them is exercising core's components, not the theme's Drive interactions with
@testing-library/user-event, notfireEvent— it dispatches the full event sequence a real interaction produces, so a test can't pass on an event a user could never fire on their own. It's a rootdevDependency; don't add it to a package:import { userEvent } from '@testing-library/user-event'; const user = userEvent.setup(); // module level, after the importsOne instance per file is the convention here, but it carries pointer and keyboard state across every test in that file. A test that presses without releasing —
user.keyboard('{Shift>}'),user.pointer({ keys: '[MouseLeft>]' })— leaks that held key or button into the tests after it, which then silently get shift-clicks they never asked for. Release it in the same test, or setuserup in abeforeEachso each test starts clean.Then
await user.click(...),await user.type(...),await user.selectOptions(...),await user.clear(...), and make the enclosingtest/itcallbackasync. A theme'sSelectis usually a custom combobox rather than a native<select>, so click the option rather than reaching forselectOptions.On a native
<select>,user.selectOptions(select, x)matches an option's text before itsvalueattribute. RJSF stores option values as enum indices ('0','1', …) while the text is the enum value, so select by the enum label: an oldfireEvent.change(select, { target: { value: 2 } })on enum[1, 2, 3]becomesuser.selectOptions(select, '3'), not'2'.A test that replaces
element.focuswith a spy (to observe RJSF's focus-on-error) must install it after anyuser.type()/user.click()on that element. user-event focuses throughelement.focus(), so with the spy in place first the keystrokes land ondocument.bodyand the input stays empty. Have the spy still focus, asvi.fn(() => HTMLElement.prototype.focus.call(input)): focus-on-error reads a no-opfocus()as the element refusing focus and moves on to the field's next control.user.type()is not the only way to set a value, and reaching forfireEventthe moment it misbehaves is the common mistake.await user.click(input)followed byawait user.paste(value)sets the whole value in a single input event, which is what you want whenever per-keystroke behavior gets in the way: jsdom's value sanitization fordate/time/datetime-localinputs rejecting intermediate characters, an assertion countingonChangecalls, or a controlled input whosevalueprop never updates and so reverts each keystroke.user.upload()coverstype=file. Seepackages/core/test/StringField.test.tsxfor bothfireEventstays correct in a few places. Give every one you write or keep a comment saying why, so the next reader doesn't "fix" it back — a handful of older calls in@rjsf/corepredate this and still lack one, so treat an uncommented call as unreviewed rather than as a precedent. Reach for it only when user-event genuinely can't express the interaction, and confirm that's true rather than assuming it:- user-event's own input model can't produce the value, whatever you drive it with. It only edits the types in its
editableInputTypeslist (text, date, datetime-local, email, month, number, password, search, tel, time, url, week), soclick+pasteon atype=colorinput silently does nothing. And every edit to atype=timeinput is rebuilt by itsbuildTimeValue, which strips non-digits and caps the result atHH:MM—'11:10:12'becomes'11:59'— so a seconds-precision time can only be set withfireEvent.change. Note thattabIndex={-1}is not a case of this: it only removes an element from the tab order, and a click still focuses it in a browser and in user-event, souser.click()followed byuser.keyboard('{Enter}')reaches atabIndex={-1}element's ownonKeyDownguard - a widget rendered with a fixed
valuethat never updates, where the re-render after each click reverts the last one — a multiple<select>needs its options selected together and reported in one change - a component whose behavior depends on the interaction being synchronous. Mantine's
Selectis the live example: its dropdown applies floating-ui'shide()middleware, jsdom lays every element out at zero size, and anyawaitlets that recomputation setdisplay: nonesogetByRole('option')finds nothing fireEvent.submitwhen clicking the real button would focus it, blurring the focused field and firingonChangebefore submit;submitForminpackages/core/test/testUtils.tsxtakes aforceFireEventflag for exactly this
- user-event's own input model can't produce the value, whatever you drive it with. It only edits the types in its
- Never relax an assertion to make a conversion work — keep
fireEventand say why instead. Watch for assertions that quietly stop testing anything: a negative one (expect(onChange).not.toHaveBeenCalled()) passes just as happily when the event never reached the element, and anexpect(...).not.toThrow()wrapping a now-asyncbody can't just becomeawait expect(promise).resolves.not.toThrow()— React routes an error thrown inside a handler to a windowerrorevent rather than rejecting the promise user-event returns, so that form passes either way. Assert on a windowerrorlistener instead, aspackages/daisyui/test/DateTimeWidget.test.tsxdoes - user-event hangs under Vitest's fake timers, and neither
advanceTimersnordelay: nullavoids it — the wait isn't user-event's.@testing-library/react'sasyncWrapperdrains the microtask queue with asetTimeout(resolve, 0)after every user-event call, and only pumps the clock when it sees a globaljest, which Vitest doesn't define. With the timer functions faked, thatsetTimeoutnever fires. A test that only needs the clock pinned should fakeDatealone:vi.useFakeTimers({ toFake: ['Date'] }) - Snapshot tests in
@rjsf/snapshot-testsare shared across theme packages, but the snapshots themselves live with each theme they render: core's in@rjsf/snapshot-tests/test(core can't depend on the package that depends on it), the 9 themes' in their own packages. Changing a shared case or core rendering means runningpnpm run test:updatefrom the root, then reviewing all 10 diffs
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

