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
{{ message }}
Repository navigation
API Platform writes: dedicated input DTO vs application command as input?
#2985
In a Symfony + API Platform project with pragmatic hexagonal architecture, what is usually recommended for write operations?
Is it better to keep:
a dedicated API HTTP input DTO / payload representing the HTTP contract
a separate application Command representing the application / use-case contract
or is it acceptable to use the application Command itself as the API Platform input?
More specifically:
when should the HTTP API contract and the application contract stay as two separate objects?
when is it reasonable to collapse them into a single Command used directly as API input?
if we use the Command as input, does that weaken an important architectural boundary even if dependency direction still remains Infrastructure -> Application -> Domain?
in both approaches, when is a custom Processor recommended?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
In a Symfony + API Platform project with pragmatic hexagonal architecture, what is usually recommended for write operations?
Is it better to keep:
or is it acceptable to use the application Command itself as the API Platform
input?More specifically:
All reactions