Gutenberg, REST API, and you

Fancy yourself some challenging architectural puzzles? Have we got the ticket for you! As you may know, Gutenberg uses the WordPress REST API as a bridge between the land of JavaScript and land of PHP. There were a whole host of conceptual challenges in translating WordPress internals to REST — and even more we still haven’t solved!
We’d love your help Read through and comment on the issues linked below as you have time. Then, if you’re available, join the next REST API office hours for a rousing conversation: April 26, 2018 5:00:00 PM GMT
Category, tag, and taxonomy controls don’t respect the correct capabilities
A user should be able to set terms on a post if they have assign_terms, and can create new terms if they have assign_terms for a non-hierarchical taxonomy, or edit_terms for a hierarchical taxonomy. However, capabilities are evaluated at runtime which means we can’t use them declaratively in Gutenberg. It would be nice if there was some existing REST paradigm we could incorporate.
Support for automatically iterating paginated resources in core-data
Gutenberg has a new withSelect() JavaScript API to fetch data from the REST API. Problems
Source: https://managewp.org/articles/17357/gutenberg-rest-api-and-you

source https://williechiu40.wordpress.com/2018/04/24/gutenberg-rest-api-and-you/