Numerical superevent parameters returned as strings

{u'created': u'2018-04-06 20:26:52 UTC',
 u'em_events': [],
 u'gw_events': [u'T0066', u'T0064', u'T0063', u'T0059'],
 u'labels': [u'LUMIN_NO', u'EM_READY', u'H1OPS', u'EM_Throttled'],
 u'links': {u'emobservations': u'TBD',
  u'events': u'https://gracedb-dev1.ligo.org/api/superevents/S0001/events/',
  u'files': u'https://gracedb-dev1.ligo.org/api/superevents/S0001/files/',
  u'labels': u'https://gracedb-dev1.ligo.org/api/superevents/S0001/labels/',
  u'logs': u'https://gracedb-dev1.ligo.org/api/superevents/S0001/logs/',
  u'self': u'https://gracedb-dev1.ligo.org/api/superevents/S0001/',
  u'voevents': u'https://gracedb-dev1.ligo.org/api/superevents/S0001/voevents/'},
 u'preferred_event': u'T0063',
 u'submitter': u'tanner.prestegard@LIGO.ORG',
 u'superevent_id': u'S0001',
 u't_0': u'12.000000',
 u't_end': u'23.234354',
 u't_start': u'56.000000'}

mentioned in merge request !8 (merged)

I believe this is resolved by overriding the rest_framework parameter 'COERCE_DECIMAL_TO_STRING' and setting it to False. See 88815c51.

Will this affect other gracedb API calls? If so, then this change might break a lot of different things.

The events portion of the API should be OK because it doesn't use the built-in object serialization features offered by the rest_framework package, which is what this parameter applies to.

closed

mentioned in issue #31 (closed)

mentioned in commit 561a915f

mentioned in commit 19a19c24

mentioned in commit a76f7811

mentioned in commit 0ca9c77b

mentioned in commit 94bf4a03

mentioned in commit bd9d5886

mentioned in commit d43a6cc2

mentioned in commit 5467bdaa

mentioned in commit e1b682ed

mentioned in commit 1e9e4944

mentioned in commit c227b3fd

mentioned in commit 84c9551f

mentioned in commit e7689679