Project

General

Profile

Actions

Defect #7427

closed

Use one xml schema per entity type

Added by Andrey Bruggemann about 13 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
REST API
Target version:
-
Start date:
2011-01-24
Due date:
% Done:

0%

Estimated time:
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>

Actions #1

Updated by Filou Centrinov almost 11 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?

Actions #2

Updated by Toshi MARUYAMA almost 11 years ago

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

Updated by Jan Niggemann (redmine.org team member) over 8 years ago

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

Also available in: Atom PDF