Allow the ability to re-order designs [Backend 2]
This a backend issue for #34382 (closed).
The backend work is split in two in order to have the work done in parallel by two developers (see #34382 (comment 354102800)).
This issue represents the backend work of this chart #34382 (comment 353297559) to add:
- Policy changes, adding a new ability
:reorder_designs
withdeveloper
level access. See: !37860 (merged) - Service for setting the order: !37603 (merged)
- GraphQL mutation: !37603 (merged)
The position will not be exposed, as it is an internal detail. To discover the order, clients should request the list of designs after mutation.
See #34382 (closed) for more details.
Note that the developer assigned to this issue will need to work closely with the developer assigned to #221167 (closed), particularly because that issue contains the database migration and finder changes. You may need to work with a mock finder, and local database changes, in order to work in parallel until the MRs from that issue are merged.
Testing Activity
- Test GraphQL works
@.luke Unit tests
- DesignsFinder
- DesignType
- GraphQL mutation (including authorization)
Request tests
- GraphQL mutation
Security Testing Activity
- Permission check in service
MR Breakdown
- 1 MR (migration)
- 1 MR (service)
- Update DesignsFinder
- Expose design order in DesignType
- GraphQL mutation