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

Organising frontend API methods #179

Open
jq1836 opened this issue Oct 19, 2024 · 0 comments
Open

Organising frontend API methods #179

jq1836 opened this issue Oct 19, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@jq1836
Copy link

jq1836 commented Oct 19, 2024

Actually, should we lump all api related methods into 2 main files, one for question-service, the other for user-service, instead of maintaining 1 file for 1 method?

Originally posted by @SelwynAng in #174 (comment)


I think that would be a good idea too, that way we have lesser files to maintain and imports will be cleaner. Let's do this in another PR. At the same time, we could also convert all existing ones requests that are still not in the lib directory, e.g. In auth-context. I'm thinking we could also move the fetchers into this file too to make everything cleaner.

Originally posted by @jq1836 in #174 (comment)

@jq1836 jq1836 added the enhancement New feature or request label Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant