Update README details, update Firebase to latest version #237
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jordanarldt
previously approved these changes
Apr 30, 2025
Meeploo
force-pushed
the
jwarren-sample-app
branch
from
969d401 to
4780851
Compare
jordanarldt
approved these changes
Apr 30, 2025
|
Looks good! Thanks for the contribution 😄 I'll need you to sign your commit before I'm able to merge |
Meeploo
force-pushed
the
jwarren-sample-app
branch
from
4780851 to
5de6dcc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
This PR updates the README to add new details about using
ngrokand a newer version offirebase. It also clarifies some steps that caused issues when following this tutorial.Why?
Several steps in the tutorial were not entirely clear.
The previous version of
firebaseno longer functioned as expected, and the new design is easier to follow.This repo is referenced in our Getting Started guide in the Developer Portal, so it should be up to date.
Testing / Proof
@bigcommerce/api-client-developers