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'm wondering if fields like channel and action in the Operation Trait Object should be there or not. These fields in the trait are optional, but in the normal Operation Object are required. I have a problem with this from a validation point of view - since the mentioned fields in the Operation Object are required then they must be defined, that is, first we would have to check if the traits are written correctly, then perform traits merging and then perform Operation Object validation. In the case of the tool ecosystem in JS, this should not be problematic, but the logic will be more complex. For other programming languages, I am afraid that implementing the above logic will be problematic.
I think we should remove the channel and action fields from the Operation Trait. We also need to take into account how traits merging works. If we define a channel in the Operation Object and in one of the traits also we will define some channel field, these channels will be merged as objects - here again there is a problem because we would have to operate on an unresolved version of the document during validation.
I'm wondering if fields like
channel
andaction
in theOperation Trait Object
should be there or not. These fields in the trait are optional, but in the normalOperation Object
are required. I have a problem with this from a validation point of view - since the mentioned fields in theOperation Object
are required then they must be defined, that is, first we would have to check if the traits are written correctly, then perform traits merging and then performOperation Object
validation. In the case of the tool ecosystem in JS, this should not be problematic, but the logic will be more complex. For other programming languages, I am afraid that implementing the above logic will be problematic.I think we should remove the
channel
andaction
fields from theOperation Trait
. We also need to take into account how traits merging works. If we define achannel
in theOperation Object
and in one of the traits also we will define somechannel
field, these channels will be merged as objects - here again there is a problem because we would have to operate on an unresolved version of the document during validation.cc @fmvilas
The text was updated successfully, but these errors were encountered: