[ckan-dev] Ckan JSON output

[Toby Dacre]

On 27 June 2013 15:08, Ian Ward <ian at excess.org> wrote:
> On Thu, Jun 27, 2013 at 4:35 AM, Toby Dacre <toby.okfn at gmail.com> wrote:
>> JSON output from the api has been changed to now display utf-8 chars
>> correctly in https://github.com/okfn/ckan/pull/846 This is targeted at
>> CKAN 2.2 unless Adriá feels like taking it for 2.1
>>
>> output was:
>>  {..., "type": "Jeu de donn\u00e9es (S\u00e9rie de donn\u00e9es)" , ...}
>>
>> new output:
>>  {..., "type": "Jeu de données (Série de données)", ...}
>>
>> This may cause some problems for existing applications using the api
>> but the change feels worthwhile.  The only changes to the tests was
>> `msg = msg.decode('utf-8')` in one file
>
> I strongly support the indenting and sort changes, they make it
> possible for people without "jsonview" or other browser extensions to
> view make manual api calls with their browsers and sensibly read the
> results.  It also makes comparing those results easier.
>
> I agree that UTF-8 encoding of the output is desirable, but is
> breaking the API for some users in a point release acceptable?  Not
> everyone can update their code so easily.

It would be easy enough to have a config option that enables this change

I think the reality is that ckan is still not as stable as we would
like and sometimes things are going to change in a point release but
they should not in a patch eg 2.0.1 -> 2.0.2


>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev



-- 
Toby Dacre

The Open Knowledge Foundation

Empowering through Open Knowledge
http://okfn.org/  |  @okfn