-
Notifications
You must be signed in to change notification settings - Fork 2.2k
feat(schematics): ng-add schematics #1853
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
Conversation
27e48e8
to
00f3a6e
Compare
00f3a6e
to
ac6251c
Compare
docs/install-and-setup.md
Outdated
@@ -2,6 +2,8 @@ | |||
|
|||
> Using Ionic and the Ionic CLI? Check out these [specific instructions](ionic/cli.md) for Ionic and their CLI. | |||
|
|||
> Following instructions use `ng add` command that automates several steps for you. If you want to set up things manually refer to [these steps](install-and-setup-manual.md) instead. |
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.
Typos:
- "Following instructions" -> "The following instructions"
- "use
ng add
command" -> "use theng add
command" - Add a comma to "If you want to set up things manually"
docs/install-and-setup.md
Outdated
|
||
- `AngularFirestoreModule` | ||
- `AngularFireAuthModule` | ||
- `AngularFireDatabaseModule` | ||
- `AngularFireStorageModule` | ||
- `AngularFireMessagingModule` (Future release) | ||
|
||
#### Adding the Firebase Database and Auth Modules | ||
### 4. Edit Firebase config in environments variable |
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.
Probably simpler to just say "Edit Firebase configuration"?
docs/install-and-setup.md
Outdated
storageBucket: '<your-storage-bucket>', | ||
messagingSenderId: '<your-messaging-sender-id>', | ||
}, | ||
production: false, |
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.
Remove the leading comma here
docs/install-and-setup.md
Outdated
@@ -141,16 +81,14 @@ import { AngularFirestore } from 'angularfire2/firestore'; | |||
@Component({ | |||
selector: 'app-root', | |||
templateUrl: 'app.component.html', | |||
styleUrls: ['app.component.css'] | |||
styleUrls: ['app.component.css'], |
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.
Once again, remove the leading comma here.
docs/install-and-setup.md
Outdated
@@ -162,7 +100,7 @@ import { Observable } from 'rxjs'; | |||
@Component({ | |||
selector: 'app-root', | |||
templateUrl: 'app.component.html', | |||
styleUrls: ['app.component.css'] | |||
styleUrls: ['app.component.css'], |
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.
Remove leading comma here
schematics/src/ng-add/schema.json
Outdated
"path": { | ||
"type": "string", | ||
"format": "path", | ||
"description": "The path to the project.", |
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.
You should be more specific here. Do you mean the project's root, or something else?
e989ad5
to
e1dfe23
Compare
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
1 similar comment
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
e1dfe23
to
a5e5129
Compare
CLAs look good, thanks! |
CLAs look good, thanks! |
Thanks @Chan4077, I've made the requested changes. |
8ce49cc
to
b85643d
Compare
Hey @sulco! Thank you so much for taking this task on! Unfortunately it's a little big of bad timing with our switch to the |
Hi @davideast! Yeah, I've seen that 😳Well, waiting is hard but actually leaving things undone is much worse, so full support to the plan. Let's wait for that landing and pick it up from there. |
7f0d9a7
to
19b446e
Compare
Ok @davideast, I've adjusted the code with the |
Hi Guys, Would be lovely if you finish this PR for |
Thanks everybody for the good work :) Any updates or ETA for this, please? /cc @davideast @Chan4077 @sulco |
Why the ping @IOAyman? I'm not a collaborator of this project. |
I can update this over the weekend so it doesn't break travis, and take a look if it still works after all these months, but other than that it's out of my hands. |
@sulco That'd be great, thanks. Hopefully a collaborator will merge and release it soon. @Chan4077 Sorry, my bad. |
It looks like this needs a rebase now. I'd love to see this get in soon so that it could get tweaked a bit more (in a separate PR) for Angular version 8. |
A possibility to install and configure the package with `ng add angularfire2` command closes angular#1676
e775eea
to
4d3b35d
Compare
Hey, @Splaktar! Apologies for taking so long and thanks for the encouragement - I've just rebased it, updated relevant dependencies to the latest + updated the PR's description on how to try the functionality out. Hopefully we're closing in on this one! :) |
"@angular/common": ">=6.0.0 <8", | ||
"@angular/compiler": ">=6.0.0 <8", | ||
"@angular/core": ">=6.0.0 <8", | ||
"@angular/platform-browser": ">=6.0.0 <8", | ||
"@angular/platform-browser-dynamic": ">=6.0.0 <8", | ||
"bufferutil": "^3.0.3", |
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.
Just wondering, but what is bufferutil
needed for here?
Thank you for pointing this one out @Chan4077 - tbh I don't remember, it's been so long since I've created this PR. I'll look that one up with once I gather the remaining feedback. On this note. Are there any plans to have this reviewed and merged any time soon @Splaktar / @davideast? The new versions of - well, everything - are coming and going, and tbh I don't know if there is a point of just keep rebasing this PR every now and then ;) |
@jamesdaniels Looking at https://twitter.com/mgechev/status/1128164567459274752 I'm not sure if this work is relevant anymore - looks like you've got Kinda disappointing tbh. Anyways, please close/reject/... this PR if that's the case. Doesn't make sense to keep this one hanging. |
Yes, I agree that not accepting or even reviewing this PR, letting it sit for 6+ months, and then re-doing the work in a separate branch/PR is NOT how open source should work. It does not provide a good experience to skilled contributors who spend a large amount of spare time to help the project. I understand that resources to maintain this repo are very limited, but that's even more of a reason that work like this should have been leveraged. @jamesdaniels please try to find a way to ensure that something like this doesn't happen again 😞 Additionally, please set expectations properly for contributors in the docs here and when you are at conferences. If PRs, or certain types of PRs, won't be reviewed or accepted, then that needs to be communicated in order to avoid wasted time, frustration, etc. |
I still believe there is value in this PR. As the ng-add and deploy commands as they exist on master don't overlap with the functionality of this PR. As mentioned on Apr 25th, I'd like to see if we can combine the efforts. Sorry for the lack of communication here, I too was caught off guard by the ng-deploy addition. |
Also I don't believe communicating when I'm at conferences will be terribly useful, as that's pretty much my job 😝 think I'm on track to hit 30 this year. TBH I thought @davideast had this one and that was a failure in our communications. We are ramping up additional team members on the project and I simplified the release process with CI/CD (pending the Angular team allowing me to create the git triggers), which should help our agility. |
I think that there was some kind of misunderstanding here. It sounds like you are responding to a request for you to let contributors know when you will be at conferences. That wasn't at all what I was meaning. Let me try rephrasing it... When you are at conferences (as you mentioned, frequently), please talk about the expectations that contributors to |
@Rofer11607 I don't think that this issue has anything to do with the changes in this PR by @sulco, which have not been merged. |
Closing in favor of #2836, where I brought over the feature initialization and environment config changes from this PR. Couple more things left to do but I'll include in 7.1, cutting a release candidate soon. |
@sulco sorry it took so long to get this one merged in. Thanks for your contribution, you've been co-authored in the big schematics commit.
In #2836 I've modernized with the new API & really amped up the |
Oh snap, thanks @jamesdaniels! I think that that's the longest "better late than never" I've ever experienced :D |
Checklist
yarn install
,yarn test
run successfully? yes (yes/no; required)Description
This adds
ng add
command that simplifies adding and setting up AngularFire to Angular apps.It follows the practices described in the current setup instructions. I've also updated these to include the
ng-add
command (the "manual" instructions are still left available though).Code sample
To try this functionality out, in the project's folder run:
npm run build
cd dist/packages-dist
npm link
Then create a sample Angular project wherever (ng new angularfire-dummy) and in that directory run
npm link @angular/fire
ng add @angular/fire
This is my first contribution here but I've tried to be careful about preparing this - if you find anything unclear though, or in a need of change, please do bug me;)