Open LevelbossMike opened 3 years ago
@LevelbossMike have you considered to make xstate lazy-loaded? not sure how it will play with XState being peerDependency
@SergeAstapov not sure how embroider would handle this. should probably work based on route splitting - are you making use of this already today?
This issue is meant as a tracking issue for all the things we want to do in the near future. The plan is to make it transparent what things are being actively worked on and things that we feel will benefit the project in the mid-term. This issue can also be an entry point for people that want to help out with ember-statecharts but don't know where to start and give people an understanding of what we feel are the most important things to improve in the near future.
Roadmap
dependency
of the addon automagically The way we are bundling XState in the project as adependency
is an idiomatic way for an ember-addon but pretty weird in the greater scheme of things. We want to simply tell people that XState is currently a dependency of ember-statecharts and that people need to pull it into their project to use ember-statecharts. Declaring XState apeerDependency
should be good enough for this use-case and as far as I understand is also the way that embroider would expect addons to be setup.ember-usable
ember-could-get-used-to-this is the new version of ember-usable. We want to use this in host applications that are using Ember.js > 3.25. To make this work we need to refactor the way we are creating the usable. This will add a very small burden on current users of the addon where they will need to change the way they are invokinguseMachine
slightly when upgrading to an ember-statecharts version that usesember-could-get-used-to-this
. We want to provide a codemod for the switch to make it easy for people to upgrade. This is a minor refactor but is currently blocked byember-cli-addon-docs
. Thanks @NullVoxPopuli for his first spike on this!Summary
@pangratz and I have big things planned for this addon this year and are very excited to make it even easier to use statecharts in Ember.js applications :rocket:. Please let us know your thoughts on the roadmap and questions if things are unclear or you want to jump into helping with ember-statecharts but don't really know where to start.