A well-thought structure is helpful for the maintainability of the code.
It also helps to avoid some common anti-patterns.
A redux application is not necessary a big thing, it can also be a component that is complex enough to require redux.
There are the only 2 rules to comply with, so it is not painful to always have them in mind while developing.
The 0.13.0 improvements to React Components are often framed as "es6 classes" but being able to use the new class syntax isn't really the big change. The main thing of note in 0.13 is that React Components are no longer special objects that need to be created using a specific method (createClass()). One of the benefits of this change is that you can use the es6 class syntax, but also tons of other patterns work as well!
Below are a few examples creating React components that all work as expected using a bunch of JS object creation patterns (https://github.com/getify/You-Dont-Know-JS/blob/master/this%20&%20object%20prototypes/ch4.md#mixins). All of the examples are of stateful components, and so need to delegate to React.Component for setState(), but if you have stateless components each patterns tends to get even simpler. The one major caveat with react components is that you need to assign props and context to the component instance otherwise the component will be static. The reason is
-moz-appearance to none. This will "reset" the styling of the element;text-indent to 0.01px. This will "push" the text a tiny bit[1] to the right;
| <?php | |
| /* | |
| * Sample code for using WordPress as a REST API endpoint (vs AJAX Admin) | |
| * Author: Pete Nelson @GunGeekATX | |
| * | |
| * 1) Create a page called API in WordPres | |
| * 2) Create a file called page-api.php in your theme directory | |
| * 3) Add code as-needed | |
| * | |
| */ |