API changes, specifically changesets.xml and the changed-files attribute, etc

[Brian Muse]

For the /changesets.xml endpoint, previously an attribute would be returned for changed-files, changed-dirs and changed-properties that contained YAML. In fact, the documentation still reflects this for the XML api. 

However a new XML format is being returned for this data. This is causing our app Beansprout to break on startup, as it looks for the response to be in a different format. Is there an flag that allows us to return the data in a backwards compatible format while we make the changes necessary to update the app?

On a similar note, the changelog used to serve a resource for staying up to date with any changes made to the API. It looks like it hasn't been updated in about a year, though.

Thanks,

Brian

[Brian Muse]

On a further note, the new response seems a little strange itself. Below is an example.

<changed-files type="array">

<changed-file type="array">

<changed-file>app/scripts/app.js</changed-file>

<changed-file>edit</changed-file>

</changed-file>

</changed-files>

Note that "edit" is listed as a changed file, when clearly that should be meta related to the <changed-file> above it.

[Ilya sabanin]

Hey Brian,

Thanks for reaching out. This is a bug and we are going to fix it shortly. Our API docs is a definitive guide.

Thanks,

Ilya Sabanin

Lead Developer 

--
You received this message because you are subscribed to the Google Groups "Beanstalk API Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beanstalkapp-api-de...@googlegroups.com.
To post to this group, send email to beanstalkapp-...@googlegroups.com.
Visit this group at http://groups.google.com/group/beanstalkapp-api-developers.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Brian Muse]

Thanks for the follow up! Any rough ETA for the fix that I can communicate to our users having the issue?

[Ilya sabanin]

It's scheduled to go out today.

ilya

On Tue, Jun 25, 2013 at 6:07 PM, Brian Muse <br...@onemightyroar.com> wrote:

Thanks for the follow up! Any rough ETA for the fix that I can communicate to our users having the issue?