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
From what I see, requirements for conditional fields are not formally specified, so it's application specific and should generate runtime error when in application logic the rules violation is detected.
So my take on that is:
for the generated API messages this is the same as optional, since it should support cases of those fields omitted
for the "reflection" way to inspect schema (easyfix-dictionary crate?), those fields might be good to mark as conditionally required, so user could treat them specially or at least know about them
From https://www.fixtrading.org/online-specification/introduction/#message-and-component-definitions
Messages are comprised of required, optional and conditionally required (fields which are required based on the presence or value of other fields) fields. Systems should be designed to operate when only the required and conditionally required fields are present.
So they should just be treated as optional for the code gen part
The text was updated successfully, but these errors were encountered: