Problem
The current implementation of FrappeClient in poc-frappe-api/src/FrappeClient.ts only supports get and post requests. To provide full REST method coverage and allow the sync engine or offline app to perform resource mutations (e.g., updating student progress, deleting draft responses), we need to support full REST capabilities.
Proposed Solution
Extend the FrappeClient wrapper with standard method signatures for the remaining HTTP verbs:
async put<T>(url: string, data?: any, config?: AxiosRequestConfig): Promise<T>
(Similar signatures should be implemented for patch and delete operations).
- The wrappers should preserve the existing typed response behavior used by the current
get and post implementations.
- The new methods should follow the same request/response normalization and interceptor flow already used by existing client methods (such as credentials injection and handling auth errors).
Acceptance Criteria
Problem
The current implementation of
FrappeClientin poc-frappe-api/src/FrappeClient.ts only supportsgetandpostrequests. To provide full REST method coverage and allow the sync engine or offline app to perform resource mutations (e.g., updating student progress, deleting draft responses), we need to support full REST capabilities.Proposed Solution
Extend the
FrappeClientwrapper with standard method signatures for the remaining HTTP verbs:(Similar signatures should be implemented for
patchanddeleteoperations).getandpostimplementations.Acceptance Criteria
FrappeClientimplements and exports standard typedput,patch, anddeletemethods.