Page Comparison

...

The REST API layer is still under design. Different idea ideas has been proposed up to know now, but still we are not sure which is the best one to adopt for the project.

Initally, the

Jira Legacy
server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-4

has been was proposed. Then the

Jira Legacy
server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-6

has started and divided in into a number of subtasks.

One of these subtask (the

Jira Legacy
server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-118

) 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.

Jira Legacy
server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-178

and

Jira Legacy
server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f0d90336-9135-337c-8387-a97c21b1155f key OP-127

)

So now the point is to adopt one of the two, with an agnostic comparison between differnt contributionsdifferent solutions.

Relevant data

• almost 90% of ModelDTOs in “api” would be identical to Models in “core”

• some ModelDTO (10%) may need a dedicated mapping

• the Swagger documentation need to be coherent with the code

Options considered

...