Re: [PATCH v4 09/10] REST API: expose patch.checks

On 20 May 14:17, Andy Doan wrote: > Signed-off-by: Andy Doan Reviewed-by: Stephen Finucane ___ Patchwork mailing list Patchwork@lists.ozlabs.org https://lists.ozlabs.org/listinfo/patchwork

Re: [PATCH v4 07/10] REST: Add Patch Checks to the API

On 20 May 14:17, Andy Doan wrote: > This exports patch checks via the REST API. > > The drf-nested-routers package is used to handle the fact Checks are > nested under a Patch. > > Security Constraints: > * Anyone (logged in or not) can read all objects. > * No one can update/delete objects. >

Re: [PATCH v4 06/10] REST: Add Patches to the API

On 20 May 14:17, Andy Doan wrote: > This exposes patches via the REST API. > > Security Constraints: > * Anyone (logged in or not) can read all objects. > * No one can create/delete objects. > * Project maintainers are allowed to update (ie "patch" >attributes) > > NOTE: Patch.save was ove

Re: [PATCH v4 05/10] REST: Add Users to the API

On 20 May 14:17, Andy Doan wrote: > This exports user objects via the REST API. > > Security Constraints: > * The API is read-only to authenticated users > > Signed-off-by: Andy Doan This needs more data to be useful, IMO. > --- > patchwork/rest_serializers.py| 8 > patchwork/t

Re: [PATCH v4 04/10] REST: Add Persons to the API

On 20 May 14:17, Andy Doan wrote: > This exports person objects via the REST API. > > Security Constraints: > * The API is read-only to authenticated users > > Signed-off-by: Andy Doan > --- > patchwork/rest_serializers.py| 13 +- > patchwork/tests/test_rest_api.py | 54 >