You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: