Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define an abstract data api #9

Open
jchartrand opened this issue Feb 2, 2024 · 0 comments
Open

Define an abstract data api #9

jchartrand opened this issue Feb 2, 2024 · 0 comments
Labels
enhancement New feature or request minor

Comments

@jchartrand
Copy link
Contributor

Move all of the data calls (mongo CRUD) to a well defined (OpenAPI/Swagger) RESTful interface, so that others can more easily understand how to substitute their own calls or backends.

Also, right now there is at least one LEF coded call that uses local Payload libraries - it should use the api endpoints like other LEF calls:

https://github.com/digitalcredentials/admin-dashboard/blob/03428e947ae7e6f20d4f2121155b1ec73c8d921e/services/payload/src/payload.config.ts#L97-L112

Aside from those api calls, there are also payload specific calls that are buried in the payload front end code ( like for creating new batches, users, templates). These should ideally be extracted to their clearly defined API, alongside every other api call.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request minor
Projects
Status: Admin Dashboard Backlog
Development

No branches or pull requests

2 participants