|
|
6 年之前 | |
|---|---|---|
| .. | ||
| Example | 1df5574c4f Upgrade gRPC-C++ to 1.28.0 (#4312) | 6 年之前 |
| Protos | 1df5574c4f Upgrade gRPC-C++ to 1.28.0 (#4312) | 6 年之前 |
| Source | 7a58eba2e5 Remove `firebase/firestore` from paths in Firestore/core (#5374) | 6 年之前 |
| Swift | b90ddf1339 Limit Swift line lengths to 100 (#5315) | 6 年之前 |
| core | b1685197db Fix GoogleTest failure mechanism on CI (#5444) | 6 年之前 |
| fuzzing | 7a58eba2e5 Remove `firebase/firestore` from paths in Firestore/core (#5374) | 6 年之前 |
| third_party | b90ddf1339 Limit Swift line lengths to 100 (#5315) | 6 年之前 |
| CHANGELOG.md | b12835caee Manually specify the authorization header (#5420) | 6 年之前 |
| CMakeLists.txt | 2a8d069b77 Run integration tests from CMake on mac (#4276) | 6 年之前 |
| README.md | 96de8fb74b Add LLDB type summaries for Firestore types (#5407) | 6 年之前 |
| test.sh | 5930ad2fee Factor out a universal build script (#884) | 8 年之前 |
Set up a workspace via CocoaPods
$ cd Firestore/Example
$ pod update
$ open Firestore.xcworkspace
Select the Firestore_Tests_iOS scheme
⌘-u to build and run the unit tests
You can install a set of type formatters to improve the presentation of
Firestore internals in LLDB and Xcode. Add the following to your ~/.lldbinit file:
command script import ~/path/to/firebase-ios-sdk/scripts/lldb/firestore.py
(substitute the location of your checkout of the firebase-ios-sdk.)
GoogleServices-Info.plist
file in Firestore/Example/App.Note: this does not give full coverage, but is much faster than above. b/hotlists/1578399 tracks outstanding issues.
GoogleServices-Info.plist is back in its default state (git
checkout Firestore/Example/App/GoogleServices-Info.plist).Install the Firebase CLI. Essentially:
npm install -g firebase-tools
Install the Firestore emulator. Essentially:
firebase setup:emulators:firestore
Run the emulator
firebase serve --only firestore
In Xcode select the Firestore_IntegrationTests_iOS scheme
⌘-u to build and run the integration tests
Typically you should not need to worrying about regenerating the C++ files from the .proto files. If you do, see instructions at Protos/README.md.