allow alternate typenames and relationships

[championswimmer]

This is to handle the case, where some server side serialization libraries might mixup singular and plural type names.

An example are these two nodejs libraries

https://www.npmjs.com/package/jsonapi-serializer - produces plurals
https://www.npmjs.com/package/json-api-serializer - produces singulars

We can now support multiple types

@Type({"comments", "comment"})
public class Comment {
	@Id
	private String id;
	private String body;
	// ...
}

Signed-off-by: Arnav Gupta [email protected]

[championswimmer]

@aggarwalpulkit596

[championswimmer]

Hey @jasminb could you take a look at this please :)

Thanks

[jasminb]

@championswimmer This looks like a useful improvements, however instead of changing the Type annotation to an array and breaking things for all of the users, I would rather add another attribute to the annotation, eg. alternativeNames which could than be used by people who need it and all existing users don't need to change anything.

[championswimmer]

@championswimmer This looks like a useful improvements, however instead of changing the Type annotation to an array and breaking things for all of the users, I would rather add another attribute to the annotation, eg. alternativeNames which could than be used by people who need it and all existing users don't need to change anything.

Well, ok that makes a lot more sense !