-
-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: implement a way of matching the fields to the jsonapi spec #983
Conversation
8b916fd
to
774579c
Compare
I think it's ready for a review 😅 |
774579c
to
21de881
Compare
21de881
to
c869008
Compare
c869008
to
beb5862
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gonna remove this one after merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you for the review. As a curiosity @AlexVanderbist how does one run the tests ? I'm happy to have a separate PR for this if it helps, or at least learn how you guys run the tests internally.
Hey @CoolGoose, thank you for taking the time to make this more compatible with the base JSON API specification and Timacdonald's package. Although it adds some complexity, I'm happy to merge it since the tests are passing and no breaking changes have been introduced. |
Hello folks, this is just a PoC (that I am cleaning up as we speak) of figuring out if there's interest on another config option to allow mapping closer to the JsonAPI spec and making this easier to use from the start with https://github.com/timacdonald/json-api