chore: add test for error when calling getData() on an in-memory request#1551
chore: add test for error when calling getData() on an in-memory request#1551MantisClone wants to merge 11 commits intomasterfrom
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughThe pull request modifies the Changes
Suggested Reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
* expect(received).toBe(expected) // Object.is equality
If it should pass with deep equality, replace "toBe" with "toStrictEqual"
Expected: {"_events": {}, "_eventsCount": 0, "_maxListeners": undefined, Symbol(kCapture): false}
Received: serializes to the same string
|
We discussed this and created a new issue to fix it. |
Motivation
The In-Memory Request docs mentioned that we cannot call
getData()on an In-memory request and I wanted to write a test to prove this is true.Changes
Summary by CodeRabbit
RequestNetworkfunctionalitygetDatamethod behavior withskipPersistenceoption