Part 2 is my fresh report of the behaviour I noticed.
I don't know enough about Redux to tell if the first approach can be fully relied on in regular Redux or it is just very probable to work. In either case, I observed this amendment was necessary when migrating to webext-redux.
An explanation might be interesting. For now I believe that a warning is better than nothing. A more elegant soulution would be welcome too, I guess.
If this needs a longer discussion, I can open an issue.
tshaddix
commented
5 years ago
Part 1 is just #179 written down
Part 2 is my fresh report of the behaviour I noticed.
I don't know enough about Redux to tell if the first approach can be fully relied on in regular Redux or it is just very probable to work. In either case, I observed this amendment was necessary when migrating to
webext-redux.An explanation might be interesting. For now I believe that a warning is better than nothing. A more elegant soulution would be welcome too, I guess. If this needs a longer discussion, I can open an issue.