You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be nice if ResourceAssembler toResource[s] method allowed a Map<String,?> to be passed in with the entity to support more complex link creation. This would allow for creating links nicely with linkTo(Class controller, Map parameters). E.g.
D toResource(T entity, Map<String,?> params)
Without it, it seems we either need to create an instance of the ResourceAssembler each time so that we can get the params in or post process (e.g. with a ResourceProcessor). I'm happy to submit a pull request if this is something of interest?
On a side note... is there a mailing list where such things are discussed beforehand? and... thanks for Spring HATEOAS!
The text was updated successfully, but these errors were encountered:
As to altering the API I'll have to research that.
Regarding naiiing list, there is none. We do most design through issues discussions and our internal Slack. When it reaches 1.0, that might be a good time to open a Gitter channel?
It'd be nice if ResourceAssembler toResource[s] method allowed a Map<String,?> to be passed in with the entity to support more complex link creation. This would allow for creating links nicely with
linkTo(Class controller, Map parameters)
. E.g.Without it, it seems we either need to create an instance of the ResourceAssembler each time so that we can get the params in or post process (e.g. with a ResourceProcessor). I'm happy to submit a pull request if this is something of interest?
On a side note... is there a mailing list where such things are discussed beforehand? and... thanks for Spring HATEOAS!
The text was updated successfully, but these errors were encountered: