|
|
2 anni fa | |
|---|---|---|
| .. | ||
| Backend | 1658c4051e Fix 9.0.0 Functions Error Code Regressions (#9862) | 3 anni fa |
| Sources | ffc697be0e [Functions] Fix typo in `HTTPSCallableOptions` initializer (#11318) | 2 anni fa |
| Tests | 0cbe4f2920 Firebase App Check One-time Use Tokens for Callable Functions SDK (#11270) | 2 anni fa |
| CHANGELOG.md | 0cbe4f2920 Firebase App Check One-time Use Tokens for Callable Functions SDK (#11270) | 2 anni fa |
| README.md | e74765ae08 Canonical directory structure for Functions (#8918) | 4 anni fa |
Follow the subsequent instructions to develop, debug, unit test, and integration test FirebaseFunctions:
pod gen FirebaseFunctions.podspec --local-sources=./open gen/FirebaseFunctions/FirebaseFunctions.xcworkspaceOR these two commands can be combined with
pod gen FirebaseFunctions.podspec --auto-open --gen-directory="gen" --cleanYou're now in an Xcode workspace generate for building, debugging and testing the FirebaseFunctions CocoaPod.
Choose the FirebaseFunctions-Unit-unit scheme and press Command-u.
Before running the integration tests, you'll need to start a backend emulator for them to talk to.
npm installed.Backend/start.sh
It will use npm install to automatically download the libraries it needs
to run the Cloud Functions Local Emulator.
The first time you run it, it will ask for a projectId.
You can put anything you like. It will be ignored.pod install.open FirebaseFunctions.xcworkspace