We only support 'Check' creation - not check updating. As a result,
there's no real reason that the 'Check.user' field should be read-only
and this is causing an issue with Django REST Framework 3.7. Simply
remove the attribute and extend the tests to validate things are working
as expected.
Signed-off-by: Stephen Finucane <stephen@that.guru>
Reviewed-by: Daniel Axtens <dja@axtens.net>
Signed-off-by: Daniel Axtens <dja@axtens.net>
(cherry picked from commit
c9cc59dac70d76971a5342ca53e2b13eb93592de)
url = CheckHyperlinkedIdentityField('api-check-detail')
patch = HiddenField(default=CurrentPatchDefault())
- user = UserSerializer(read_only=True, default=CurrentUserDefault())
+ user = UserSerializer(default=CurrentUserDefault())
def run_validation(self, data):
for val, label in Check.STATE_CHOICES:
self.assertEqual(check_obj.target_url, check_json['target_url'])
self.assertEqual(check_obj.context, check_json['context'])
self.assertEqual(check_obj.description, check_json['description'])
+ self.assertEqual(check_obj.user.id, check_json['user']['id'])
def test_list(self):
"""Validate we can list checks on a patch."""