this has been corrected in latest development version so will be okay in 2.16. It is not intentional but also not completely arbitrary - all those classes implement a common “dimensional” interface and as a result ended up with wrong re-directs. The Web API has undergone a rewrite for 2.16 so unfortunately we are not able to back-port the “fix”.
regards,
Lars
···
On Sun, Jul 6, 2014 at 1:36 PM, Lavi Shpigelman shpigi@gmail.com wrote:
Hi.
I noticed that in in version 2.15 (and also in version 2.13), some of the resources in the api/resources page point to the same url (api/dimensions)
Lars, is there an intention to fix this bug in 2.15 ? I understand that the Web API is being rewritten but this is a major bug. Or is 2.15 not to be regarded as a stable release, with the userbase being encouraged to move directly to 2.16?
- Edward -
···
On Sunday, July 6, 2014 7:17 PM, Lars Helge Øverland <larshelge@gmail.com> wrote:
Hi Lavi,
this has been corrected in latest development version so will be okay in 2.16. It is not intentional but also not completely arbitrary - all those classes implement a common "dimensional" interface and as a result ended up with wrong re-directs. The Web API has undergone a rewrite for 2.16 so unfortunately we are not able to back-port the "fix".
regards,
Lars
On Sun, Jul 6, 2014 at 1:36 PM, Lavi Shpigelman <shpigi@gmail.com> wrote:
Hi.
I noticed that in in version 2.15 (and also in version 2.13), some of the resources in the api/resources page point to the same url (api/dimensions)
These include:
<resource name="Categories" href="DHIS2 App Hub;
<resource name="CategoryOptionGroupSets" href="DHIS2 App Hub;
<resource name="DataElementGroupSets" href="DHIS2 App Hub;
<resource name="DataElements" href="DHIS2 App Hub;
<resource name="Dimensions" href="DHIS2 App Hub;
<resource name="OrganisationUnitGroupSets" href="DHIS2 App Hub;
<resource name="TrackedEntityAttributes" href="DHIS2 App Hub;
Is this intentional or should each of the resources point to a url with the resource name (only camelCased)
I’m sorry but we don’t plan to fix this. If you let us know your use-case we are happy to suggest a work-around.
regards,
Lars
···
On Tue, Jul 22, 2014 at 9:32 AM, Edward Ari Bichetero ebichete@yahoo.com wrote:
Lars, is there an intention to fix this bug in 2.15 ? I understand that the Web API is being rewritten but this is a major bug. Or is 2.15 not to be regarded as a stable release, with the userbase being encouraged to move directly to 2.16?
Edward -
On Sunday, July 6, 2014 7:17 PM, Lars Helge Øverland larshelge@gmail.com wrote:
Hi Lavi,
this has been corrected in latest development version so will be okay in 2.16. It is not intentional but also not completely arbitrary - all those classes implement a common “dimensional” interface and as a result ended up with wrong re-directs. The Web API has undergone a rewrite for 2.16 so unfortunately we are not able to back-port the “fix”.
regards,
Lars
On Sun, Jul 6, 2014 at 1:36 PM, Lavi Shpigelman shpigi@gmail.com wrote:
Hi.
I noticed that in in version 2.15 (and also in version 2.13), some of the resources in the api/resources page point to the same url (api/dimensions)
These include:
Is this intentional or should each of the resources point to a url with the resource name (only camelCased)