Defect #7427

Use one xml schema per entity type

Added by Andrey Bruggemann almost 9 years ago. Updated about 4 years ago.

Status:ClosedStart date:2011-01-24
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:REST API
Target version:-
Resolution:No feedback Affected version:

Description

Would be better if find (GET) and create/update (POST/PUT) methods use the same xml schema, for each entity type.
For example, the xml schema for issue creation are:

<issue>
  <subject>Example</subject>
  <project_id>1</project_id>
  <priority_id>4</priority_id>
</issue>

But should be:
<issue>
  <subject>Example</subject>
  <project>
    <id>1</id>
  </project>
  <priority>
    <id>4</id>
  </priority>
</issue>

History

#1 Updated by Filou Centrinov over 6 years ago

Category: REST API
Status: Feedback / Closed

The REST API for issues has been improved. It was't implemented as you proposed, but I think the current version could satisfy you. Can we close this issue?

#2 Updated by Toshi MARUYAMA over 6 years ago

  • Category set to REST API
  • Status changed from New to Needs feedback

#3 Updated by Jan Niggemann (redmine.org team member) about 4 years ago

  • Status changed from Needs feedback to Closed
  • Resolution set to No feedback

Also available in: Atom PDF