-
Notifications
You must be signed in to change notification settings - Fork 57
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 the ApiKeyComponent
code in the dashboard
#465
Labels
good first issue
Good for newcomers
refactoring ♻️
A code change that neither fixes a bug nor adds a feature
Comments
vplasencia
added
the
refactoring ♻️
A code change that neither fixes a bug nor adds a feature
label
Mar 31, 2024
So just remove the function call to getadmininfo() function? |
Hey @code-Gambler! Yes, the idea would be to remove the |
Yup it does, I will work on it. You can assign it to me! |
Great! Done. Thanks. |
2 tasks
PR submitted! |
2 tasks
aguzmant103
added
good first issue
Good for newcomers
and removed
good first issue
Good for newcomers
labels
Jun 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for newcomers
refactoring ♻️
A code change that neither fixes a bug nor adds a feature
Description
Every time, the functions
handleRefresh
andtoggleIsEnabled
are called, there are two requests to the Bandada API. Just one request is required, the one related to updating the info in the backend (updateApiKey
), the other to get the admin information (getAdmin
) shouldn't be necessary since all the info is already in the frontend.The idea is to write the component in a way that only the
updateApiKey
request is sent to the Bandada API.The text was updated successfully, but these errors were encountered: