-
-
Notifications
You must be signed in to change notification settings - Fork 211
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
Compile a Matrix Showing Implementations' Adherence to the Suite #20
Comments
This is where the changes to the list of implementations reached so far: All github information being pulled from site at real time. Have you given the storage of matrix results any thought? I played around with a way to capture unit test results from travis, as well as anyone else running a test and keeping revisions of the results with totals etc on github itself. It can be accomplished with the [github database api[(http://developer.github.com/v3/git/) and you can see the results from some initial bashing at the problem can be seen here https://github.com/Respect/Foundation/issues/26#issuecomment-12614405 works like a charm. This information we can then pull into the table results in a similar fashion. Savvy? |
Uh, I cannot read this table at all :/ And the version of my library reported is "prehistoric" as well. OK, I update it at a frantic pace, but care to explain what the different columns mean? |
I haven't thought about how to do this yet, no. json-schema.org is hosted on github which limits how dynamic we can be I guess. Have to think about this more. Welcome to hear more comments. |
I'm a bit late to the party, but could you use a build server (eg Travis-ci) to run the test suite then push the results to the github site (via an api) which could then save them to the database for rendering later? |
Or better yet, set up an api to receive results, and issue each project with a secret key to access the api. Then get them to push their own results as part of their regular build. Might be a lot easier to maintain that way |
Perhaps close this in favor of json-schema-org/website#125 on the grounds of keeping all info about implementations in one place (the web site)? |
Sounds good to me.
…On Sep 25, 2017 6:18 PM, "Henry Andrews" ***@***.***> wrote:
Perhaps close this in favor of json-schema-org/website#125
<json-schema-org/website#125>
on the grounds of keeping all info about implementations in one place (the
web site)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAUIXggd3Bm1JdGY2gxLZd3ffrHMDZoEks5smCacgaJpZM4AZAnF>
.
|
See json-schema-org/json-schema-org.github.io#16
The text was updated successfully, but these errors were encountered: