PushType API development

Tags: #<Tag:0x00007f81c68b21b8>

(Aaron Russell) #1

PushType requires an full REST api. This will primarily be used by the admin engine, so we can redesign and redevelop the admin UI (moving a bit closer to a SPA), but the API should also be the basis for external integrations.

I’ll keep this topic up to date with a spec as it forms, progress and any related features/issues.


Restful resources

  • Nodes: CRUD actions plus delete, restore, trash, reorder :heavy_check_mark:
  • Assets: CRUD actions plus delete, restore, trash :heavy_check_mark:
  • Users: CRUD actions :heavy_check_mark:

Other dev required

  • Nestable concern should validate a node’s parent accepts it as a child :heavy_check_mark:
  • Add authentication hooks to auth engine :heavy_check_mark:
  • Should admin controllers be namespaced the same way api controllers are for consitency? (seems to me they should be, even if the routes are not namespaces) :heavy_check_mark:
  • Refactor admin js to use new API endpoints and remove api-like actions from admin. :heavy_check_mark:
  • Shared admin/api controller methods should be put in a shared concern in Core.

PushType development roadmap
(Aaron Russell) #2

Commits for Restful resources:

(Aaron Russell) #3

(Aaron Russell) #4

Integrated with auth engine.

(Aaron Russell) #5