You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect the attributes to be an object, since it's defined like this: required(:attributes).maybe(:hash). It is, in fact, an array.
I would expect attributes to require the name since it's defined like this required(:name).filled(:string, min_size?: 1). It is, in fact, not required.
Affects my production application: NO
Ruby version: 3.1.1
OS: Mac OS Monteray (M1)
The text was updated successfully, but these errors were encountered:
In other terms, it looks like the nested hash definition is overridden by the higher level array definition. I would expect to be able to change type as I build out the schema.
Describe the bug
Given these two dry schemas:
I would expect to se a JSON schema like this:
But, in fact, I see JSON like this:
There are two, principle differences:
attributes
to be an object, since it's defined like this:required(:attributes).maybe(:hash)
. It is, in fact, an array.attributes
to require thename
since it's defined like thisrequired(:name).filled(:string, min_size?: 1)
. It is, in fact, not required.The text was updated successfully, but these errors were encountered: