Jasmin Begic
Jasmin Begic
@green-arrow I would say yes; however, it has interesting consequence in context of resource resolution, eg. referenced resource is a 'top-level' resource. Should we use the top level resource for...
@green-arrow my bad, this already works properly. I guess, only thing left to do would be to implement a change in order to avoid double-serialisation of resources.
@bvalentino1 will take a look as soon as I get some time and will merge/comment.
Hey, Thanks for reporting and providing steps to reproduce. Will take a look and fix it.
Hey @crcsaenz, Will try to fix it soon, its not a simple fix due to how caching/parsing is done.
Hey, I've considered lazy loading already. Having in mind that lib is used for android dev also and networking restrictions that come with it, executing lazy resolution becomes really tricky.
Hey @emetsger, yes it is something that has its uses. Please have in mind that introduction of `JsonApiDocument` that I am currently working on will change some stuff, so maybe...
Hey, Library was not written with JAX-RS in mind, however, you should be able to implement `MessageBodyReader` so you can handle multiple types correctly, eg. resolve target type dynamically and...
Hey @emetsger, All your points are valid, current state of the lib does not allow for paginated relationship handling. Lib should allow both options: eager fetching (your solution) and a...
Hello, Support for accessing `parent` is not there, here is why: - both parent and child should be first class citizens on your API Parent path example: `/v2/parent/{id}` Child path...