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
code in #1497 added a CommandResultBuilder that makes it easier and more reliable to create the CommandResult
However we still need to:
convert the CommandResult to a class, move the builder to be inner, and protect the constructor so it can only be created using the builder.
make the resolvers create the CommandResultBuilder in inject into the operations (I think) or do something else so we are reliably detecting if debug mode is set. See CommandResult.singleDocumentBuilder() for comments.
we may not need / want to though, the OperationAttempt framework uses a page builder that already uses this CommandResultBuilder so it may not be necessary to make changes only for collections right now.
this ticket is to remember, and decide if we want to make the change
The text was updated successfully, but these errors were encountered:
Changes the warnings associated commands to use the new ApiExcpetions,
and `warnings` in the return status now returns a list of error object V2.
To do that needed to improve the way CommandResult was built, so it always
had a status map so the CommandProcessor could append a warning. To do that
expanded the CommandResultBuilder added for the OperationAttempts, removed
the many overloads used for CommandResult, and updated all creation of the
CommandResult to use the builder.
See also #1518 to continue this
code in #1497 added a CommandResultBuilder that makes it easier and more reliable to create the CommandResult
However we still need to:
CommandResult.singleDocumentBuilder()
for comments.this ticket is to remember, and decide if we want to make the change
The text was updated successfully, but these errors were encountered: