Caveats

Issues just pointing at the current caveats of the plugin

A ticked checkbox means, this has been handled and is now doable in the plugin

- [x] Binary Expressions (`$a+=1`,`$a = $a+1`) (`$text = $text + "A"`)
- [x] Update Expressions (`$a++`,`$a--`) for numbers
- [x] Member Expressions on all types ( `$text = $text.toUpperCase()` ) ()
- [ ] Pragma changing, (let's say you want to use preact instead of react)
- [ ] you'll have to create your own setters when passing around the state to other functions / returning it from a function. [Check this issue](https://github.com/barelyhuman/babel-plugin-mutable-react-state/issues/5)

Review the unchecked caveats, especially pragma changing and setter creation when state crosses function boundaries. Start with the linked issue about custom setters; the payload names no source files or tests. Done would require defining and implementing the missing behavior, then documenting or checking off the supported caveats.

Written by the indexing model from the issue text.