Hi devs, I’d like to make 2 changes to the Resource module that are breaking (but this module has @Unstable annotations so it should be ok): * Change 1: Move getAction() to Resource. Right now it’s only in EntityResource but I’d like that each Resource has an action associated to it. I also propose that we use a GET action for the single action that currently exist for non Entity Resources (for example for skin resources). * Change 2: I’d like to type more the Resource action and introduce a ResourceAction class (exactly similar to the Syntax class in the Rendering). The idea is to have a list of well-known resource actions and at the same time be able to create new actions. This is better than constantly comparing and using strings. So for example this means that instead of the following in Resource (currently in EntityResource but see change 1):     /**      * @see #getAction()      */     private String action; we would have:     /**      * @see #getAction()      */     private ResourceAction action; WDYT? Barring any negative comments, I’ll implement this in the coming days. Thanks -Vincent