JSON fields in changesets API?

I am the developer of the Rust redmine-api crate and I noticed today that due to a bug I had never implemented the changeset include value for the Issues REST API

Since we are not using this feature in our redmine instance I have no easy way to get an example object here and the documentation does not contain an example either. I tried to check the Redmine source code but the Rails syntax is not familiar enough to be sure what is a field
in the JSON output and what isn't and which objects might be what I dubbed *Essentials types in my crate (just id and name for display purposes).

If someone is using this feature or is a Redmine developer could you maybe show me one (or a few if there are significant differences between different VCS changesets) example(s) so I can build support for this? If you do have edit permissions for the wiki here adding it right to the REST API docs would be great, if not just responding here would be fine too though.

Replies (2)

RE: JSON fields in changesets API? - Added by Bernhard Rohloff about 9 hours ago

Hi Matthias,

nice to see somebody working on growing the Redmine ecosystem. Unfortunately I have no Git repository to try at the moment. Subversion is way easier as redmine.org has one integrated.
Nonetheless I had ha quick look into the sources (source:trunk/app/views/issues/show.api.rsb@22846#L46) and it seems there's no difference in the output between the different version control systems. So my recommendation would be, just to implement what redmine.org has to offer like for this query: https://www.redmine.org/issues/43396.json?include=changesets

Greetings,
Bernhard

RE: JSON fields in changesets API? - Added by Matthias Hörmann about 7 hours ago

Thank you. I had not considered that the redmine.org instance had that integration active and a publicly accessible API.

I have added the changesets feature as a 0.9.1 release of my crate now.

(1-2/2)

Project

General

Profile

Redmine