REST: top priorities for Drupal 8.2.x

Added another issue which could be interesting: #2721595: Simplify REST configuration

Hello can this be added to this list #2653318: While in maintenance mode, REST routes respond with HTML instead of XML/JSON/…?

@Wim IMHO #2310307: File needs CRUD permissions to make REST work on entity/file/{id} would be a critical issue here if we want to upload files. AFAIK we want to create 2 entities in the same request and avoid to create the File and then the node(or the custom entity). @alexpott told me that we want to avoid the current solution("everybody can upload files").

And #1927648: Serialize file content (base64) to support REST GET/POST/PATCH on file entity uses this patch...

Adding another issue to it: #2228141: Add authentication support to REST views

One more for consideration #2758897: Consider moving rest link manager services into serialization module

I just wanted to try highlight a list of issue that would be great to get done before the Feature freeze for 8.2.0-beta1. I think this is Week of August 3, 2016.

Issues that are new Features or tasks, not listing but because I don't think they are affected by the freeze.

Very Close - could be done by deadline
#2403307: RPC endpoints for user authentication: log in, check login status, log out with related #2753681: Move CSRF header token out of REST module so that user module can use it, as well as any contrib module
#2291055: REST resources for anonymous users: register

Not as close
#1927648: Serialize file content (base64) to support REST GET/POST/PATCH on file entity
#1869548: Opt-in CORS support
#2664780: Remove REST's resource- and verb-specific permissions for EntityResource, but provide BC and document why it's necessary for other resources

Seems unlikely
#2099281: [PP-1] REST views: pagination link relations
#2300677: [PP-1] Create/Update/Delete (POST/PATCH/DELETE) ConfigEntity via REST
#2135829: EntityResource: translations support

Not started but does is this test so is it affected by feature freeze? #2737719: EntityResource: Provide comprehensive test coverage: for every entity type, every format, every method

BTW: I could be totally wrong about above. Let me know. I was partly doing it for my own benefit to figure out what is the most important to work on.

#2113345: Define a mechanism for custom link relationships is an issue someone could review. If someone needs something special: #1928868: Typed config incorrectly implements Typed Data interfaces is up there for review. This will enable POST/PATCH of config entities.

Especially the later would be nice because we need probably a full release to add the required constrains so we can start supporting updates.

I can't review #1928868: Typed config incorrectly implements Typed Data interfaces — that needs review from a Typed Data maintainer.

It almost feels as if noone could review it :)

for another step toward api first & truly decoupling, voting for: #2771353: Support "auto-create" entity references by value (instead of by ID/UUID), just like tags are auto-created in the content creation UI

show stopper: #2772413: REST GET fails on entity/taxonomy_vocabulary/{id} 403 Forbidden with error

@jacov
One thing you always have to keep in mind. Critical in an issue doesn't mean its critical for you, but rather the site. Each major is most likely a critical issue aka. show blocker on actual sites, but we cannot treat Drupal core as a union of sites. This simply doesn't scale.

Thank you @Wim Leers for cleaning up this mess!

Good idea. In general there are also things which are pure bug fixes, that can land more or less at any point, and there are more task/featurish things, which should be prioritized in the next 2 weeks.

After trying to use the new configuration entity based system, I think we should fix #2777969: Provide an example REST configuration entity