-
Notifications
You must be signed in to change notification settings - Fork 320
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
[Refactor] Frontend API Calls should be kept under the Service
folder
#917
Comments
Hey @Kajol-Kumari Please assign the admin folder to me. |
Hey @Kajol-Kumari I’ll take the QnA folder for refactor. Please assign this to me. |
@Faizanusmani06 and @devmusiczz please feel free to open the respective issue and continue on the same, Happy Learning :) |
assign me this issue |
@Hemxnt u need to mention the module, please go there issue description properly |
@Kajol-Kumari can you please assign me the contactUs folder. |
@Kajol-Kumari can you please assign me the about folder |
@Kajol-Kumari can you please assign me faq folder |
@shivamgaur99 / @Hemu21 assigned the respective modules, please feel free to open the respective issue and continue on the same, Happy Learning :) |
@Kajol-Kumari can you please assign me the resources folder. If possible can you please assign me the Broadcast also |
@Kajol-Kumari can you please assign me the Broadcast folder |
@Kajol-Kumari Since the FAQ folder also contains Q&A-related files, I worked on both FAQ and Q&A in my recent pull request. Can you check it? I didn't see that anyone is already assigned for Q&A. |
Describe the bug
Currently, all the API calls is taking place atleast twice, one for normal flow and one for admin.
Expected behavior
We should keep all the api calls in a single folder
service
and then reuse the same code for all the places.This issue just a placeholder as there are multiple folders that needs refactoring, so anyone who claims this issue, can pick one folder at a time, i will tag them here and then raise an issue for that, it will be given
level 2
and then start working.The text was updated successfully, but these errors were encountered: