We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always
The changelog of v11.0.0 says this:
When no object is found calling Realm#objectForPrimaryKey, null is returned instead of undefined
But these two are not updated to line up with the document above. They still return undefined instead of null
undefined
null
realm-js/packages/realm-web/types/realm/index.d.ts
Line 1327 in eb91953
Line 1330 in eb91953
No response
11.9
Local Database only
Yes
All
Which debugger for React Native: ..
The text was updated successfully, but these errors were encountered:
It has been fixed in v12: https://github.com/realm/realm-js/blob/main/packages/realm/src/Realm.ts#L946-L984
You are welcome to try the latest release candidate (npm install realm@next).
npm install realm@next
Sorry, something went wrong.
No branches or pull requests
How frequently does the bug occur?
Always
Description
The changelog of v11.0.0 says this:
But these two are not updated to line up with the document above. They still return
undefined
instead ofnull
realm-js/packages/realm-web/types/realm/index.d.ts
Line 1327 in eb91953
realm-js/packages/realm-web/types/realm/index.d.ts
Line 1330 in eb91953
Stacktrace & log output
No response
Can you reproduce the bug?
Always
Reproduction Steps
No response
Version
11.9
What services are you using?
Local Database only
Are you using encryption?
Yes
Platform OS and version(s)
All
Build environment
Which debugger for React Native: ..
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: