-
Notifications
You must be signed in to change notification settings - Fork 610
fix(toJSON): get the generic type T for toJSON response #6789
New issue
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
Open
vinibgoulart
wants to merge
6
commits into
realm:main
Choose a base branch
from
vinibgoulart:feat/toJSON
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
0a5c148
fix(toJSON): get the generic type T for toJSON response
vinibgoulart 7bafc41
fix(lint): lint
vinibgoulart eb270f7
fix(return): return the generic type T
vinibgoulart ff9e13b
fix(toJSON): return realm ommited types from generic return
vinibgoulart c98e65b
feat(toJSON): accept Unmanaged generic type as toJSON return function
vinibgoulart 1959c4b
fix(type): ommited type
vinibgoulart File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your commit.
Unmanaged<T>will remap all properties to optional.If a property is not optional in its
Realm.Objectschema, instances created by that Object will certainly have that property and it will not be optional.Will this cause the object returned by
toJSON()to need to be remapped with type definitions in order to be used correctly?Maybe
OmittedRealmTypes<T>is sufficient?