Ashwin Ramaswami
Ashwin Ramaswami
This would be related to #1157
@jorisw sounds like a reasonable proposal! Would you be willing to submit a PR that fixes the naming and makes the property names more intuitive?
Not sure if we should implement this... could you look through the JSON Schema spec (https://json-schema.org/) and see what it might have to say about $ref's with a HTTPS url?
I like the idea of users being able to choose between several given $ref resolver implementations (JSON pointer, URL, or a combination of multiple ones), and also provide their own...
I did work on this in [another project](https://github.com/epicfaace/CFF/blob/622e9d8f1d44be5933ce964d094704d9ed529908/scripts/src/form/form_widgets/AutoPopulateField.tsx), so perhaps that code could be ported over to this library.
This was partially (supporting a type + a "null" type) added by https://github.com/mozilla-services/react-jsonschema-form/pull/1213
@dekelb thanks for noting this issue. I'm good with your suggestion, but just wondering about the semantics of it. I'm wondering whether to define custom options for each setting in...