json based spec for implementors to use #114
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
My opinion would be to put this into a separate repository (eg json-api/json-spec). |
|
That's the idea, after it's working. On Thu, May 30, 2013 at 8:59 PM, Brian Shirai notifications@github.com
|
|
@brixen yes I agree. Let's discuss this first here. |
Three files are provided: 1) fixtures.json Defines the data that servers must load to test reading and updating. 2) read.json Provides reading use cases. Each use case is composed of config, expectedRequest and expectedResponse config defines which fixture should be used, and other server settings like if the server ask for client-ids, uses url based style and/or compounds related objects. 3) write.json Similar to read.json
|
This is really old, and @spastorino, i'm not sure you're interested in updating it, given our recent discussions. Let's just give this a close for now. I'm not sure this problem has been figured out adequately yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
NOTE: THIS IS WORK IN PROGRESS.
I'm sending this mostly for you guys to review.
I'm implementing json-api in https://github.com/rails-api/active_model_serializers
Still not sure about many things but I guess it's better to start discussing from this point better than waiting to have a perfect thing.
The idea is to provide json files for implementors to load them, there you have the use cases and you can build tests from there.
Again these files lacks of a lot of use cases, but anyway provide all the feedback you can.
Three files are provided:
Defines the data that servers must load to test reading and updating.
Provides reading use cases.
Each use case is composed of config, expectedRequest and expectedResponse
config defines which fixture should be used, and other server settings
like if the server ask for client-ids, uses url based style and/or
compounds related objects.
Similar to read.json
Let me know your thoughts.