Jasmin Begic
Jasmin Begic
One way to tackle this would be to store raw `Node` that was deserialised into model as an attribute in `JSONAPIDocument`. New method could be added than (to `JSONAPIDocument` that...
@bensullivan, currently its not available. I could add it to the `JSONAPIDocument` and make a method available.
Hello @bensullivan, I will make the raw `Node` data available as a workaround until i get the time to come up with proper solution. Edit: This change is now available...
Hello @bensullivan, internally same logic that is used to parse primary data is used to parse relationship data and thats why the same rules apply. This should be something that...
Just tested parsing following payload (on both `master` and `develop`): ```json { "data": { "type": "engineer", "id": "id", "relationships": { "field": { "data": null }, "city": { "data": null }...
Please change the PR to include relevant code changes only, remove all formatting changes and add a unit test to cover the change.
@ExtinctAmoeba Please format the provided JSON so it can be read properly.
Hello @ExtinctAmoeba To handle this case, create an interface `Section` and then implement it for different section types. Use the `Section` interface in as a type in the class that...
@ExtinctAmoeba Ive updated README.md with an example on how to setup polymorphic relationship use-case: https://github.com/jasminb/jsonapi-converter/blob/develop/README.md#polymorphic-relationships
@ExtinctAmoeba Hopefully you were able to resolve the issue?