Skip to content
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.

Consolidate REST API planning documents and add plan for expected functionality #348

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

shannynalayna
Copy link
Contributor

This change moves the REST API design documents from community/planning/features into a rest-specific directory. Historical documents are linked from the top-level doc with descriptions on the proposed functionality.

This change updates the community planning features list to consolidate
REST API designs into one feature document. This document will speak on
the designs from the past and the future designs for the Grid REST API.

This also alphabetizes the remaining features.

Signed-off-by: Shannyn Telander <telander@bitwise.io>
This change moves feature documents for the REST API into a directory,
titled `rest_api`. These documents were unlinked from the community
features page, as the index page of this directory will link to the
historic design documents.

Signed-off-by: Shannyn Telander <telander@bitwise.io>
This change adds a description of how the REST API will handle batches,
for both gridd and griddle. This includes information on the payloads
that will be accepted by the new REST API and how specific endpoints
will respond.

Signed-off-by: Shannyn Telander <telander@bitwise.io>
This change adds short descriptions to previously proposed functionality
and links to the respective design documents.

Signed-off-by: Shannyn Telander <telander@bitwise.io>
@shannynalayna shannynalayna force-pushed the shannynalayna-update-rest-api-planning branch from 5c0e486 to 6452d92 Compare August 12, 2022 19:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant