feat(javascript): allow cache on POST #5675
Merged
+133
−15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By reordering the conditions, we now allow a POST request to explicitly be cached, even if it doesn't per se use the read requester.
Usage in customPost for example:
```
customPost({
path: '/xxx',
}, {
cacheable: true
})
```
Collaborator
No code generatedIf you believe code should've been generated, please, report the issue. 📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
Haroenv
changed the title
Fluf22
reviewed
Nov 24, 2025
.../algoliasearch-client-javascript/packages/client-common/src/transporter/createTransporter.ts
Show resolved
Hide resolved
Fluf22
approved these changes
Dec 2, 2025
algolia-bot
added a commit
to algolia/algoliasearch-client-javascript
that referenced
this pull request
Dec 3, 2025
algolia/api-clients-automation#5675 Co-authored-by: Haroen Viaene <hello@haroen.me>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🧭 What and Why
By reordering the conditions, we now allow a POST request to explicitly be cached, even if it doesn't per se use the read requester.
Usage in customPost for example:
Changes included:
🧪 Test
Added tests for the transporter