Therefore, I would like to have it embedded inside yewdux-middleware.
Given that both yewdux and this project are under Apache + MIT, I don't see an issue here.
To keep things simple, and to allow easy switching back to yewdux (if it comes back to life) I would really like to have all the crates of yewdux under a single module here named yewdux. This way, if we switch back to the upstream yewdux, we can keep the yewdux module, and it would just re-export the yewdux crate.
ALL of the 4 crates of yewdux need to be sub-modules of the new yewdux module.
Also when adding the yewdux own deps in our Cargo.toml maybe keep them a bit separate and commented as such in our toml file so that we can easily remove them later.
Therefore, I would like to have it embedded inside
yewdux-middleware.Given that both yewdux and this project are under Apache + MIT, I don't see an issue here.
To keep things simple, and to allow easy switching back to
yewdux(if it comes back to life) I would really like to have all the crates ofyewduxunder a single module here namedyewdux. This way, if we switch back to the upstreamyewdux, we can keep theyewduxmodule, and it would just re-export theyewduxcrate.ALL of the 4 crates of
yewduxneed to be sub-modules of the newyewduxmodule.Also when adding the
yewduxown deps in ourCargo.tomlmaybe keep them a bit separate and commented as such in our toml file so that we can easily remove them later.