Looks like a bug - we purposely don't allow null f...
# http4k
d
Looks like a bug - we purposely don't allow null field values in examples as we introspect the example objects to generate the schema
a
In my case I cannot create a valid example without have a null field. The body is actually a list of items which reference their parent. Root items don't have parents (thus the
null
field). In my example, one of the items has the parent field set and the other has the parent field as
null
.
Is there a way for me to provide the schema instead of it being inferred from my example?
d
nope.
it's a limitation of the current mechanism. We check for null somewhere and throw if we can't retrieve a a field value
a
OK, thanks for the feedback. Unfortunately, the current behavior is blocking me.
d
it's possible if you replaced the usage of SimpleLookup FieldRetrieval you could unblock yourself
a
Ok, I'll take a look