@radekmie Above when you say ' but a simple wrapper to ValidatedQuickForm' do you mean a class which extends it, or a component which wraps it. I am using a hooks component and wrapping a ValidatedQuickForm, managing the state inside my component and updating the
model prop when changes are made. The problem I am having is that there is a lag between changes to this model prop and the change in the form.
Console logs illustrate that each keystroke is in fact changing the state, and quickly, but the re-render seems to take place only after a brief delay and the changes are batched. This doesn't happen with a plain AutoForm which (reading the source) extends the ValidatedQuickForm and calls its setState method rather than passing through props. This difference is the only thing I can think of that might be causing input response lag. Does that sound plausible?
If that's the case I have several workarounds (we discussed above) I can employ, but I would like to understand why I am seeing this behavior
Hey guys, just started looking over your library, it looks really promising!
Just 1 quick question... I tried it out with a fairly simple JSON Schema, and I'm having trouble rendering array properties. It seems like it renders a field for it, but is not rendering the Add and Del buttons/icons, therefore I cannot add any data to the list field. Is this expected behaviour? Do I have to customize my form with
Just 1 quick question... I tried it out with a fairly simple JSON Schema, and I'm having trouble rendering array properties. It seems like it renders a field for it, but is not rendering the Add and Del buttons/icons, therefore I cannot add any data to the list field. Is this expected behaviour? Do I have to customize my form with
ListFields under the AutoForm to make this work? I'm using uniforms-bootstrap4, but the problem is the same with uniforms-bootstrap3. My JSON schema looks like this:{
"title": "Guest",
"type": "object",
"properties": {
"competencies": {
"type": "array",
"items": {
"type": "object",
"properties": {
"name": { "type": "string" }
}
}
}
}
}
^ Turns out it's because it requires the
octicons icon package to be available in the app. Overriding the .octicon selector fixed it for me. Would be nice to implement other icons such as FontAwesome, or maybe a fallback such as a '+' or a '-' when octicons aren't available.
@danyhiol It looks like we are depending on a too low version of
tslib. Could you file this in an issue, please?
@cvincent-atmanco This theme was designed some time ago and it just stuck to the Octoicons. You can use the
ListAddField (ListDelField) prop addIcon (removeIcon) to change it: https://github.com/vazco/uniforms/blob/d3f7f852c0b8d589b7415206d31448d4c54af990/packages/uniforms-bootstrap4/src/ListAddField.tsx#L24. It's really possible to detect any font icon in the component, so it won't work like that. We should definitely mention it in the docs though.
There is a strange behavior happening with 
- image. When defining an array with minCount and options, there are null entries in the array. While
arrays-field. simpleSchema requires using minCount to make an array not empty.
I think it actually worked in the past...
As always, file an issue please.
And thanks again for a report.
I've tried both
uniforms and react-jsonschema-form ... and ... only frustrations :) The idea sounds so well but I can't simply figure out how to use these libraries
Note: I'm an experienced developer using, reusing, and creating lots of packages ... and still :)
For example the example in this issue comment simply doesn't works : https://github.com/vazco/uniforms/issues/517#issuecomment-470690363 ... and it's given by the maintainer itself
And how on earth one can provide a solution without checkbox fields? https://uniforms.tools/docs/api-fields
No offense :) Just curious ... how others managed to get by ....
Does anybody is using this package generating any kind of forms coming from an API? Or is used just for simple use cases like a signup form?
It's normal that certain comments may be obsolete or simply broken with time (this comment is over 9 months old).
If you have any problems like this, just file an issue (or comment). I saw you did that already and that's great.
I've been using uniforms for a lot of generated forms, even user-defined ones so it works.
There may be (and certainly are) some problems with the docs - if you think that something should be added/changed/removed there - write it here, file an issue, or even a PR if you have time.
Hi. Quick question - is there any documentation regarding all of the properties and values that can be used when using JSON Schema? For example in https://uniforms.tools/docs/examples-common-forms there are
uniforms, const, $data, etc.
Hi @jeremypeters. In general everything without
$all/$any works. By works I mean that it'll correctly render a form and validate the input. What may not work is a correct error reporting, as some of these issues may be on a different level (e.g. parent value). If you'll have anything that won't work - do file an issue.
How to create custom schema for
Uniform (from server)
// Method
Meteor.methods({
existName(name) {
return name == 'Rabbit'
},
})
--------------
// Custom Msg
SimpleSchema.setDefaultMessages({
messages: {
en: {
CustomMsg: 'This is custom msg!',
},
},
})
// Schema
name: {
type: String,
async custom() {
const result = await Meteor.call('existValue', this.value)
if (result) {
return 'CustomMsg'
}
},
},
Just another quick question: We were hoping to use Uniforms to generate forms completely from JSON provided by our API. However it look like this is not possible, because if we need to use a component (e.g. LongTextField) this is not specified in the schema as a string. Or am I missing something?
I'm using a variety of advanced autoform components with JSON Schema bridges -- but have run up against a strange issue with nested object values. I thought everything was working until I actually tried to enter text in one of many fields I set up... somehow the onChange handler isn't accepting text for these, even though the nested object schema is valid. Is it perhaps something with the bridge? Same result with a NestField wrapper as well:
<AutoField label="Step Title" name="locale.step2Title" placeholder="eg. My Priorities" />
Hello guys. I want to separate client-side validations from backend validations. I'm used to do it using React Final Forms with submitError like this example: https://final-form.org/docs/react-final-form/examples/submission-errors
Is there any similar approach when using uniforms?
I did it using onSubmitFailure, but found it a bit painfull to have all that maping and a useState:
const [errors, setErrors] = useState(null);
return <AutoForm
schema={FornecedorSchema}
error={errors}
onSubmit={onSubmit}
onSubmitSuccess={() => setErrors(null)}
onSubmitFailure={(error) => {
if (error.response?.status === 400 && error.response.data.fieldErrors) {
setErrors({
details: error.response.data.fieldErrors.map(({ message, field: missingProperty }) => ({
dataPath: "." + missingProperty,
keyword: "required",
message,
params: { missingProperty },
})),
});
}
}}Thank you :)