refactor: move API config management to context #451
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Type of change
How Has This Been Tested?
Checklist:
Additional context
Related Issues
Reviewers
Important
Refactor API configuration management by moving logic to
ExtensionStateContextand renaming functions for clarity.onUpsertConfigtoonDuplicateConfiginApiConfigManager.tsxandSettingsView.tsx.ExtensionStateContext.renameApiConfigurationandduplicateApiConfigmethods toExtensionStateContext.ExtensionStateContext.tsxto include new methods for API config management.SettingsView.tsxfor handling API config renaming and duplication.ApiConfigManager.tsxto use newonDuplicateConfigmethod for duplicating configurations.This description was created by
for bf06b2b70bb0e0e531aeeff29592fc5bb7351720. It will automatically update as commits are pushed.