feat: add global API timeout setting and enhance force delete confirmation modal #902
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
This pull request introduces a new API timeout configuration feature and improves the force delete confirmation modal by adding a loading state to the delete button. The most important changes are grouped below by theme.
API Timeout Configuration:
setGlobalAPITimeoutmethod to theCoreAPIclass, allowing global adjustment of the API request timeout.setGlobalAPITimeoutfrom the API module for use throughout the application.Force Delete Confirmation Modal Improvements:
ForceDeleteConfirmationPropsto include an optionalisDeletingproperty, enabling loading state management for the modal.isDeletingprop to the modal component and the primary button, displaying a loading indicator during deletion. [1] [2]Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist