Form-js form field of type <undefined> not supported

nikku · August 23, 2021, 1:37pm

This is likely because you’re passing the schema as a string or pass a null schema.

We’re not 100% done with that API yet and may improve its developer friendlyness in the future. One thing it definitely lacks is proper error handling (in the sense of meaningful error messages on miss-use).

I’ve created a GitHub issue to track this:

github.com/bpmn-io/form-js

Import errors do not properly indicate miss-use

opened 01:15PM - 23 Aug 21 UTC

nikku

enhancement ux

__Is your feature request related to a problem? Please describe__ Importing a… form schema requires the schema to be already parsed as in `JSON.parse`. This is different from our other toolkits where passing the raw thing (XML string) is enough. __Describe the solution you'd like__ There is a few things to consider here, i.e. does it make sense to force a user to parse the document herself, if she is not interested in the file format at all? We're going a different path in our other libraries (string in, string out) that I tend to find better suited. The obvious easy pick is of course to properly indicate miss-use with better error messages. __Additional context__ Applies to all form-js versions `<= 5`.