Skip to content
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

Create a basic StackBlitz template #64

Open
smithad15 opened this issue Jan 8, 2019 · 2 comments
Open

Create a basic StackBlitz template #64

smithad15 opened this issue Jan 8, 2019 · 2 comments
Labels
enhancement New feature or request foundational Maintenance, tooling, etc.

Comments

@smithad15
Copy link
Member

Having a basic StackBlitz setup for the library would be useful. This could be used as a template for issue reporting or just for the community at large.

@smithad15 smithad15 added enhancement New feature or request foundational Maintenance, tooling, etc. labels Jan 8, 2019
@wtho
Copy link
Contributor

wtho commented Jan 9, 2019

I created one here a while ago. I stripped angular-redux/forms and angular-redux/router from it, as they create noise in redux without being involved in issues most of the time.

It features:

  • Current angular/redux/redux-observable/... versions
  • One component assigned to a route (home.component)
  • One simple sync action for this component triggered by a button
  • One async action with an epic which will fetch async data via HTTP, triggered by a button

Feel free to fork and link it from this repo or ask me for improvements. I would suggest to keep it simple though.

Maybe check if you can login with the angular-redux github account directly, then you can save the template in that account, making it more official.

I would also suggest to create a new repository containing that test repo. I know, this contradicts the idea of the mono-repo, but gives you full version control. As described in the docs, repositories containing an Angular project in the root can be opened using e. g. stackblitz.com/github/angular-redux/stackblitz-example. Otherwise there will always be the danger that the owning user just makes small edits without forking before, altering the opened stackblitz project immediately.

@spygi
Copy link

spygi commented May 14, 2019

This helps, thanks @wtho! Maybe it would make sense to have a link to your stackblitz in the README?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request foundational Maintenance, tooling, etc.
Development

No branches or pull requests

3 participants