Skip to content

Sublinks Native API #119

Open
Open

Description

@jgrim

Create basic CRUD restful endpoints for the core entities:

  1. Announcements
  2. Comments
  3. Communities
  4. Instances
  5. People
  6. Posts
  7. PrivateMessages

This means each resource will have a POST, PUT, GET support in the following format:
Create: POST /api/v1/{resource}
Read: GET /api/v1/{resource} & GET /api/v1/{resource}/{id}
Update: PUT /api/v1/{resource}/{id}
Delete: DELETE /api/v1/{resource}/{id}

Do not create and RPC endpoints. For example, instead of adding a moderator to a communtiy like this: POST /api/v1/community/sublinks/addModerator do it like this: POST /api/v1/community/sublinks/moderator. Then create a new Controller for moderators with CRUD actions to create, read, update, and delete moderators from a community. An update for example could change the sort order of moderators.

Activity

  1. converted this from a draft issue on Dec 21, 2023
  2. self-assigned this
    on Dec 21, 2023
  3. added this to the Version 0.1 - Parity milestone on Dec 21, 2023
  4. added a commit that references this issue on Dec 22, 2023
  5. assigned and unassigned on Apr 23, 2024
  6. linked a pull request that will close this issue#119 Native Sublinks API #359on Apr 24, 2024
  7. moved this from 🏗 In progress to 👀 In review in Sublinks Developmenton Jul 24, 2024
  8. moved this from 👀 In review to 🏗 In progress in Sublinks Developmenton Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions