The prerequisites in the Building Realm section of README.md mention:

Building Realm requires Xcode 8.x.

The current wording implies that only Xcode 8.x is supported, but Xcode 11 support landed via #6163.

This should be updated to "Xcode 8.x or newer" as appropriate for what is actually supported & tested. Since X

The encryption section in Java docs https://realm.io/docs/java/latest/#encryption leads to an example that doesn't properly provide a best practice solution for how to store keys used for encryption.

Since tslint is deprecated, we should migrate the project to use eslint with the typescript plugins instead.

See https://github.com/typescript-eslint/typescript-eslint/blob/master/docs/getting-started/linting/README.md.

This work has been (sort of) started in realm/realm-js#2794.

Original title: 修改表字段的默认值问题

![image](https://user-images.gith

Phase 1:
[ ] provider clients (email-password)
[ ] link_user
[ ] custom_data

Phase 2:
[ ] remote mongodb client
[ ] functions
[ ] push
[ ] Remaining provider clients

Details of above subtasks are described in this doc

We currently only run a few select unittests with encryption - we should extend this so that all unittests are run with encryption, at least periodically (it takes a while, so may not be needed on PR's, but master once a day for example)

Need to include:

• Consul information
• Subdirectories for each section with package files
• Move over all code samples: https://docs.realm.io/platform/self-hosted/manage/enterprise-architecture/manual-deployment-instructions