Add Database Export and Import APIs #10
Merged
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.
This pull request introduces support for new database export and import APIs, expands privilege management, and updates several API response models for consistency. It also includes minor workflow and test improvements. The most important changes are grouped below.
API Client Enhancements:
DatabaseExportApi,DatabaseExportEndApi,DatabaseExportPartApi) and import (ImportApi,ImportChunkApi) APIs inApiClient, including corresponding accessor methods. [1] [2] [3]Privilege Management:
DATABASE_EXPORTandDATABASE_IMPORTinPrivilege.php, and included them in the list of allowable enum values. [1] [2]API Response Model Consistency:
dataproperty types in user and token response models to useUserStoreResponse,UserShowResponse,UserUpdateResponse, andTokenShowResponseinstead of controller-specific response types, updating both type hints and docblocks in the relevant model files. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]Test and Workflow Improvements: