-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update readme #272
update readme #272
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mostly lgtm. but would wait on @egilmorez for word smitthing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have one major global comment on the README and related product borders. PTAL, thanks!
README.md
Outdated
| EnvVarConfig.value | string |Value associated with the environment variable | | ||
| EnvVarConfig.availability | RUNTIME | Where the variable will be available, for now this will always be RUNTIME | | ||
|
||
Many of these fields are shared with apphosting.yaml as well so see [our documentation](https://firebase.google.com/docs/reference/apphosting/rest/v1beta/projects.locations.backends.builds#runconfig) for additional context. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest:
"Many of these fields are shared with apphosting.yaml. See the runConfig reference documentation for additional context."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am I seeing an outdated diff? It looks like you did not include the suggested change (as well as various other nits)
|
||
## Overview | ||
|
||
Firebase Hosting integrates with popular modern web frameworks including Angular and Next.js. Using Firebase Hosting and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this entire overview be retooled to refer to App Hosting instead of Firebase Hosting?
iiuc, we're going to keep "supporting" framework-aware CLI via the very similar docs on Devsite, while we basically transform this particular readme and repo to pertain to FAH adapters. It will be key to distinguish the two arenas I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just a copy and past of the old docs to the subsection that they apply to. I talked to James earlier and we decided we can just keep the old docs here for now too since they still make sense for this section. I don't think either of us felt very strongly about this though, so if you think it makes sense to remove this section as a whole I'm good with that too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant to request changes on the README, thanks!
Co-authored-by: Daniel Lee <[email protected]>
Went through and addressed/responded to all comments, would love another pass thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wei, is it possible you didn't push your changes for some of these resolved comments?
Various suggestions from me and Daniel don't appear in the version I'm seeing here.
README.md
Outdated
Firebase provides this functionality through the Firebase CLI. When initializing Hosting on the command line, you | ||
provide information about your new or existing Web project, and the CLI sets up the right resources for your chosen Web | ||
framework. | ||
This repo holds the code for the adapters that enable support for these frameworks. At a high level these adapters transform frameowkr specific configurations into an output bundle spec that App Hosting is able to process and configure frameworks support. For more information see our [documentation](https://firebase.google.com/docs/app-hosting/about-app-hosting#frameworks) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this may have been an old diff, not sure what happened but these were already addressed for me locally and in the pr I saw. I just pushed another change to address a couple other changes too so could you check again and see if these are fixed now?
README.md
Outdated
| EnvVarConfig.value | string |Value associated with the environment variable | | ||
| EnvVarConfig.availability | RUNTIME | Where the variable will be available, for now this will always be RUNTIME | | ||
|
||
Many of these fields are shared with apphosting.yaml as well so see [our documentation](https://firebase.google.com/docs/reference/apphosting/rest/v1beta/projects.locations.backends.builds#runconfig) for additional context. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am I seeing an outdated diff? It looks like you did not include the suggested change (as well as various other nits)
I think they should have been pushed and addressed, the pr I saw pushed had these things addressed. Maybe some weird issue with github. Could you check again now? I just pushed some more changes to address the new comments but that should also include the old changes too. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK it looks like I'm looking at a current/fresh diff now, thanks!
One tiny nit and LGTM.
README.md
Outdated
Firebase provides this functionality through the Firebase CLI. When initializing Hosting on the command line, you | ||
provide information about your new or existing Web project, and the CLI sets up the right resources for your chosen Web | ||
framework. | ||
This repo holds the code for the adapters that enable support for these frameworks. At a high level these adapters transform framework specific configurations into an [output bundle spec](#app-hosting-output-bundle) that App Hosting can use to configure frameworks support. For more information see our [Framework integration](https://firebase.google.com/docs/app-hosting/about-app-hosting#frameworks). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: omit "our" for just "see [Framework integration]"
Left some comments, I think we should consider having optional vs. required and defaults documented |
Added optional vs required and linked out to product docs for defaults documented so we have a single source of truth still. See discussion for another decision we've made before similar to this #244 (comment) |
Update the readme with output bundle specifications information