Hi Mark,
Ok. I'll keep the test disabled for now and we can enable it again once the
fix is released on the API side.
Thanks,
Paulo
On Mon, Oct 10, 2016 at 8:28 AM Mark Polak wrote:
> Hey Paolo,
>
> We have made this action unavailable in the UI, as like Jason says, this
> is generally not som
Hey Paolo,
We have made this action unavailable in the UI, as like Jason says, this is
generally not something you would want.
I would say the test case is indeed correct. We should enforce the same
logic on the server.
On Mon, Oct 10, 2016 at 6:32 AM, Jason Pickering <
jason.p.picker...@gmail.c
Hi Paulo,
I would expect that this operation should be disallowed by the server. The
reason for this is that once you have established that a given option set
has a type "INTEGER" , you should not be able to change this afterwards to
a different type. It seems the test is correct to me, but from t
Correction:
Version: 2.*24*-20161008
On Sun, Oct 9, 2016 at 7:40 PM Paulo Grácio wrote:
> Hi devs,
>
> should it be able to update existent Option Set code from
> 'TEST_OPTION_SET' to 'TEST_OPTION_SET_NEW'?
>
> Test Case:
> https://github.com/dhis2/api-tests/blob/master/modules/data-admin/optio
Hi devs,
should it be able to update existent Option Set code from 'TEST_OPTION_SET'
to 'TEST_OPTION_SET_NEW'?
Test Case:
https://github.com/dhis2/api-tests/blob/master/modules/data-admin/optionSet.js#L62
Failing Job: https://travis-ci.org/dhis2/api-tests/jobs/166235371
Version: 2.23-20161008
BR
Hi devs,
should it be possible to update existent Option Set type from 'INTEGER' to
‘TEXT'?
Test Case:
https://github.com/dhis2/api-tests/blob/master/modules/data-admin/optionSet.js#L77
Failing Job: https://travis-ci.org/dhis2/api-tests/jobs/166211140
BR,
Paulo Grácio
___
6 matches
Mail list logo
