[PATCH 01/10] REST: Check.user is not read-only

Stephen Finucane stephen at that.guru
Wed May 1 03:49:21 AEST 2019

On Tue, 2019-04-30 at 16:02 +1000, Daniel Axtens wrote:
> From: Stephen Finucane <stephen at that.guru>
> 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 at that.guru>
> Reviewed-by: Daniel Axtens <dja at axtens.net>
> Signed-off-by: Daniel Axtens <dja at axtens.net>
> (cherry picked from commit c9cc59dac70d76971a5342ca53e2b13eb93592de)
> Signed-off-by: Daniel Axtens <dja at axtens.net>

Makes sense. Applied.

More information about the Patchwork mailing list