Which is the best pattern to use in the controller?
Background
The REST API layer is still under design. Different idea has been proposed up to know but still we are not sure which is the best one.
Initally, the OP-4 - Getting issue details... STATUS has been proposed
Then the OP-6 - Getting issue details... STATUS has started and divided in a number of subtasks
One of these subtask (the OP-118 - Getting issue details... STATUS ) changed the initial proposal to something different while not yet completed (premature merge) and while other contributors were relying on the initially proposed pattern in other isses (e.g. OP-178 - Getting issue details... STATUS and OP-127 - Getting issue details... STATUS )
So now the point is to adopt one of the two, with an agnostic comparison between differnt contributions.
Relevant data
almost 90% of ModelDTOs in “api” would be identical to Models in “core”
some ModelDTO may need a dedicated mapping
Options considered
Option 1: | Option 2: | |
|---|---|---|
Description | Linear mapping | Automapping |
Pros and cons |
|
|
Estimated cost | SMALL | SMALL |
doesn’t need more knowledge for Java Base contributors (more linear)
makes the controllers tickerAction items
These are the proposed steps in order to take a decision
- Riccardo Costa continues with the linear mapping on module “OPD” as per his own OP-118
- Uni2grow Cameroun continues with his own work on the OP-115
- Antonio Verni propose a change to the initial pattern in order to make it not exlusive and applying it on other OP-6 unassigned subtasks (e.g. OP-119)
- Vito Romano continues his own work on OP-116 trying using the the change to the initial pattern coming from Antonio
- Alessandro Domanico To decide the final pattern before the end of March