-
Notifications
You must be signed in to change notification settings - Fork 88
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
Conversion to Synced Realm only supported in PBS. #3333
Conversation
✅ Deploy Preview for device-sdk ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Readability for Commit Hash: 4925fac You can see any previous Readability scores (if they exist) by looking Readability scores for changed documents:
For Grade Level, aim for 8 or below. For Reading Ease scores, aim for 60 or above:
For help improving readability, try Hemingway App. |
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.
Overall, LGTM - we just need to add a redirect for the page we're removing, and I have a minor suggestion re: mentioning the WriteCopy API on the .NET page.
```````````````````````````````````````````` | ||
To convert a non-synced realm to a synced realm, you can follow the process | ||
described in :ref:`Migrate a Local-Only App to a Sync-Enabled App <realm-sync-local-to-sync>`. | ||
The .NET SDK also provides the |
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.
I think we should either leave this off the page entirely, or mention here that it only works with Partition-Based Sync. Mentioning that this API exists without the warning that our "default" Sync apps can't use it feels like it will lead to user frustration.
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.
Agreed. Added back in the note that was on the original 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.
I'm down with deleting this, but we should add a redirect for it if we do.
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.
Looks like there is one more spot where we need to update a redirect to avoid a redirect chain, but after that change, this LGTM!
config/redirects
Outdated
|
||
# DOCSP-39075 | ||
raw: ${prefix}/sdk/dotnet/sync/convert-realm -> ${deviceSDKsBase}/sdk/dotnet/sync/configure-and-open-a-synced-realm |
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.
In addition to adding this new one, I see there is a prior redirect that points to the convert-realm page at line 1023 - we need to update that one, too, to avoid a redirect chain.
✨ Staging URL: https://preview-mongodbmongodb.gatsbyjs.io/realm/master/ 🪵 Logs |
Pull Request Info - SDK Docs Consolidation
Jira ticket: https://jira.mongodb.org/browse/DOCSP-39075
Staged Page