Comments (5)
I think you need to declare reference to location.json differently, not using /#defs prefix.
See this comment with explanation how ajv works
from react-jsonschema-form.
Thanks for your reply, I'm using the # json pointer because according to the RJSF docs on Schema definitions and references
its the only type of ref RJSF supports
Note that this library only supports local definition referencing. The value in the $ref keyword should be a JSON Pointer in URI fragment identifier format.
After reading the json schema docs for $id
I noticed it says this:
When the $id keyword appears in a subschema, it means something slightly different. See the bundling section for more.
I don't fully understand why but after removing the $id
from the sub-schema (in $defs
) it appears to be working now
from react-jsonschema-form.
Yes, this is exactly what is explained in the comment I referenced.
Also see this issue
from react-jsonschema-form.
@jag43 Has this issue been resolved? If so, please close
from react-jsonschema-form.
Yes I've resolved this thank you for your help
from react-jsonschema-form.
Related Issues (20)
- TS Error 'FieldComponent' cannot be used as a JSX component. HOT 2
- liveOmit & omitExtraData not work with empty oneOf HOT 1
- Unable to select 0 with enum checkbox (antd only)
- Push an error from a widget HOT 6
- [chakra-ui] ui:options rows not applied for `textarea` element HOT 1
- New `enumTitles` not working => old `enumNames` have warnings ⚠️ that are depreciated 🐛 HOT 2
- Possibilty to filter properties from big json schemas HOT 2
- Allow defining custom validation error HOT 4
- Is it possible to clear form errors programatically? HOT 2
- Crash when update to v5.17.0: util could not be found within the project or in these directories HOT 5
- Consider moving omit extra data functionality to schemaUtils HOT 1
- Unable to create precompiled validators due to compileSchemaValidators HOT 2
- SSR and dependencies sections cause hydration errors. HOT 1
- setting options via ui:widget object is no longer supported, use ui:options instead HOT 3
- <>
- `Form` renders extra fields that breaks validation HOT 1
- If/then/else shows a field despite dependent condition not met HOT 2
- Bug with array properties inside allOf HOT 1
- Pass errorSchema from ArrayField to ArrayFieldTemplate HOT 2
- doc about localization of ajv incomplete for MUI forms HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from react-jsonschema-form.