Update for Rules v2: remove "Device Sync Permissions"

[cbush]

Pull Request Info

Jira

• https://jira.mongodb.org/browse/DOCSP-26779

Staged Changes

• https://docs-mongodbcom-staging.corp.mongodb.com/realm/docsworker-xlarge/permissions-v2/

Reminder Checklist

If your PR modifies the docs, you might need to also update some corresponding
pages. Check if completed or N/A.

• Create Jira ticket for corresponding docs-app-services update(s), if any
• Checked/updated Admin API
• Checked/updated CLI reference

Review Guidelines

REVIEWING.md

[github-actions]

Readability for Commit Hash: 5885ea9

You can see any previous Readability scores (if they exist) by looking
at the comment's history.

Flesch Reading Ease scores for changed documents:

• source/sdk/flutter/sync/write-to-synced-realm: 58.21
• source/sdk/swift/sync/write-to-synced-realm: 50.6

The following table can be helpful in assessing the readability score of a document.

Score	Difficulty
90-100	Very Easy
80-89	Easy
70-79	Fairly Easy
60-69	Medium
50-59	Fairly Hard
30-49	Hard
0-29	Very Hard

[cbush]

Removed because queryable fields are now automatically determined.

[dacharyc]

I thought this was only when Development Mode is enabled?

If this is true when Development Mode is enabled, we should call that out instead of just removing this - i.e. "If Development Mode is enabled, Sync can automatically determine queryable fields from your Flexible Sync query. If Development Mode is not enabled, add these queryable fields."

Related, if this is true when Development Mode is enabled, then we can probably remove this info from all of the Quick Starts? I think they all have a bullet in the Device Sync prerequisites about configuring queryable field, but they also say to enable Development Mode, so this would be unnecessary there.

[dacharyc]

Related, there is also mention of configuring queryable fields on the "Manage Flexible Sync Subscription" pages: https://www.mongodb.com/docs/realm/sdk/swift/sync/flexible-sync/#subscribe-to-queryable-fields

We might want to add something there about not needing to do this if Development Mode is enabled?

[dacharyc]

And in the "Add Device Sync to an App" page that exists in Swift: https://www.mongodb.com/docs/realm/sdk/swift/sync/add-sync-to-app/

Flutter has the same page but the verbiage there is slightly different so I don't think it needs any updates relative to queryable fields.

[dacharyc]

The changes here look fine, except I have a Q about the queryable fields. If I've misunderstood, feel free to disregard - but if my understanding is correct, I'd suggest we tweak this update and also update some related places throughout the SDK docs.

[dacharyc]

I thought this was only when Development Mode is enabled?

If this is true when Development Mode is enabled, we should call that out instead of just removing this - i.e. "If Development Mode is enabled, Sync can automatically determine queryable fields from your Flexible Sync query. If Development Mode is not enabled, add these queryable fields."

Related, if this is true when Development Mode is enabled, then we can probably remove this info from all of the Quick Starts? I think they all have a bullet in the Device Sync prerequisites about configuring queryable field, but they also say to enable Development Mode, so this would be unnecessary there.

[dacharyc]

Related, there is also mention of configuring queryable fields on the "Manage Flexible Sync Subscription" pages: https://www.mongodb.com/docs/realm/sdk/swift/sync/flexible-sync/#subscribe-to-queryable-fields

We might want to add something there about not needing to do this if Development Mode is enabled?

[dacharyc]

And in the "Add Device Sync to an App" page that exists in Swift: https://www.mongodb.com/docs/realm/sdk/swift/sync/add-sync-to-app/

Flutter has the same page but the verbiage there is slightly different so I don't think it needs any updates relative to queryable fields.

[cbush]

@dacharyc you're right, the change to queryable fields only applies to Development Mode. I undid that change, and we'll address it in the proper ticket.