-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Internal] Modular API's (in components) #177
Comments
what do you mean by outstanding APIs. A little confused. I am going to use this to understand the code base |
also when you say "respective components" do you mean, like the components folder? and not the API folder? or both? |
API calls that are not inside a component/module (basically if index.tsx is just calling an API that would be better placed inside of a component)
Sounds great! do you want me to assign you to it?
API's are called in the component files. We have the actual API functions in the /api folder, but they are called all throughout the code. (@TyHil if you want to add context?) |
That's pretty much it. Just to say it another way: There's a professor API (which really just forwards an API call to the Nebula API with the right API key) that's called from the I suppose it's important to note this PR could find that all the API calls are in the right places, as far down as they can be moved. Or not. Just good to check. |
Also where to write the documentation? as small comments or confluence? |
Confluence. Under Engineering. IMO should outline how and where we interact with APIs and how we use that data. |
Overview of Proposed Changes
What: Ensure all API calls are occurring in their respective components
Why: Modularity, cleaner code
Details
outstandingstray API calls to inside componentsThe text was updated successfully, but these errors were encountered: