-
Notifications
You must be signed in to change notification settings - Fork 26
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
Merge steps in master #93
Comments
i'll work on it. |
Not with this issue, as we don't want to impact the slides too much for now. |
As dependencies will be updated by #95, be aware that this include to update the related Angular / rxjs / ngrx code too. |
Sure : i'll update code when i'll add steps to master branch. |
Next step: |
You can use step1 for now, we'll think about that later. |
Fine. I'll wait you to merge #95 to make more pull requests (readme & steps). |
@geromegrignon #95 still have opened conversations you should address. As soon you have resolved them, I'll merge 😉 |
The only one left (not outdate or resolved) is about project architecture. |
@geromegrignon let me know if you need any help on this, as I'll give this school at the end of this month. |
first steps handled in #98 |
As it is really difficult to maintain and use so many branches, we should only use the master.
To do so, I think the better solution would be to simply use angular-cli 7 (see #92), with a common library and several "step" apps when needed, and no root project (ie. all projects should be in the project folder).
The text was updated successfully, but these errors were encountered: