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

Do not try to determine storage in API layer #944

Open
sattvikc opened this issue Mar 4, 2024 · 2 comments
Open

Do not try to determine storage in API layer #944

sattvikc opened this issue Mar 4, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@sattvikc
Copy link
Collaborator

sattvikc commented Mar 4, 2024

🐛 Bug Report

Refactor API layer in such a way that we don't need to figure out the storage in the API layer and then pass it to the function layer. Function layer should determine the storage layer by itself so that it's easy to call them from API layer and reduce mistakes with regards to which storage to use for the required purpose.

Useful informations

(Write what happened. Add screenshots, stacktraces, videos, anything that can help)

@sattvikc sattvikc added the bug Something isn't working label Mar 4, 2024
@erzohrakhan
Copy link

@sattvikc Can I work on this issue?

@sahilsekr42
Copy link

@sattvikc I just found this issue to work on but I don't seem to understand what figuring out storage in api layer here refers to . As far as I can understand the api layer probably refers to backend sdks interfacing the core or is it the interface between core and database being used and is function layer is the core . does storage layer refer to the database and where is this figuring out happening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants