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
The cond attribute appears to only work with Option fields, at least when dealing with custom types. It seems reasonable to assume that any type that implements Default should support conditional parsing. Also, there's no indication that the cond attribute is not doing anything for these types - we only realised this after carefully going through the trace logs.
Switching from cond = "expression" to skip, cond = "!expression" instead seems to give the expected result for arbitrary types.
The text was updated successfully, but these errors were encountered:
The
cond
attribute appears to only work withOption
fields, at least when dealing with custom types. It seems reasonable to assume that any type that implementsDefault
should support conditional parsing. Also, there's no indication that thecond
attribute is not doing anything for these types - we only realised this after carefully going through the trace logs.Switching from
cond = "expression"
toskip, cond = "!expression"
instead seems to give the expected result for arbitrary types.The text was updated successfully, but these errors were encountered: