profile
viewpoint
Sam Parsons sjparsons @braintree USA http://sjparsons.com Software engineer

APIs-guru/graphql-over-http 80

Working draft of "GraphQL over HTTP" specification

sjparsons/housetopia 25

Example app with React Router v4 and animations

sjparsons/example-react-app-with-create-react-app 7

A step by step (see the tags) example of building a React app with Create React App for a lightning talk at React Minneapolis

sjparsons/Google_WebSearch 4

A PHP class for interacting with Google's JSON Search API for Flash and other Non-Javascript Environments

sjparsons/apache-log-analysis 1

Toolkit for analyzing apache logs.

sjparsons/ia-doc 1

IA-Doc

sjparsons/bright 0

Bright theme for Shower HTML presentation engine

sjparsons/challenge-framework 0

A framework for testing JavaScript code against a set of requirements

sjparsons/checker 0

A self-contained system for running web services checks.

sjparsons/custom-actions-docs 0

Custom Actions documentation

issue commentAPIs-guru/graphql-over-http

Find the best time for the GraphQL over HTTP working group

Just a quick reminder folks: please fill out the doodle link above with your availability so that we can get the best time to meet going forward.

@abernix @balshor @benjie @deinok @ErikWittern @jaydenseric @michaelstaib @mike-marcacci @mmatsa @sjparsons @spawnia @sungam3r @enisdenjo

sjparsons

comment created time in 3 days

issue openedAPIs-guru/graphql-over-http

Mechanism for optional features

It's come up a number of times in our discussions as a working group: We would like to have optional features that can be adopted and if adopted by a server/client then that section of the spec can be applied. I believe we need a mechanism for this.

  1. Documentation: we need to add a section to help organize and specify these optional features
  2. Communication: Servers need to communicate which features they support and clients need to communicate what features they wish to use.

I know we wish to leave many of the optional features to be defined after the 1.0 release, but I'm wondering whether the mechanism should/could be put in place for the 1.0 release, so that we have a firm foundation and clear runway after the 1.0 to start building extensions and optional features.

I'm interested in hearing (1) opinions on 1.0 or post 1.0 release and (2) ideas about possible solutions for the 2. Communication mechanism described above.

created time in 3 days

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha cce3e8b6886fc60619db1c457dc714a1069982d4

Create July 2020 Agenda

view details

push time in 8 days

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha b562f3953aae907f34cc71c0effa5b3c64976d6a

Add permanent zoom link for meetings

view details

push time in 8 days

push eventAPIs-guru/graphql-over-http

Michael Staib

commit sha bcf4f89b5ffebf8169af169b590dab2b38cd7e89

Added extensions to the graphql request (#4) * Added extensions to the graphql request * Update README.md Co-Authored-By: Ivan Maximov <sungam3r@yandex.ru> * Update README.md Co-Authored-By: Ivan Maximov <sungam3r@yandex.ru> Co-authored-by: Ivan Maximov <sungam3r@yandex.ru>

view details

push time in 8 days

PR merged APIs-guru/graphql-over-http

Added extensions to the graphql request

Hi Ivan,

I have added the extensions property to the request.

Also shouldn't we describe how the response should look like?

+3 -0

6 comments

1 changed file

michaelstaib

pr closed time in 8 days

issue commentAPIs-guru/graphql-over-http

X-GraphQL-Event-Stream for being notified that the GraphQL schema has updated

This is a fascinating idea. I really like it. I can also see that it'd be nice to see a standard around this mechanism. I'm thinking it'd be best for this to be post-1.0 release. What do you think?

benjie

comment created time in 8 days

issue commentAPIs-guru/graphql-over-http

"application/graphql" as official MIME type

A couple of notes:

  1. We intend to use this new content type in the 1.0 release of the GraphQL over HTTP spec, based on consensus at the last few working group meetings.
  2. We will not necessarily pursue getting it an official MIME type per se before the 1.0 of the GraphQL over HTTP spec.

So I have marked this issue as post 1.0 release milestone as that's when intend to pursue the official MIME type.

IvanGoncharov

comment created time in 8 days

issue closedAPIs-guru/graphql-over-http

Actions from 2020-05-26 meeting

Based on the 2020-05-26 working group meeting, here's the planned actions we'd like to work on next. If you're tagged here and you feel you cannot meet that commitment, please comment or DM me. Also, if you'd like to get involved on any of these actions just post.

(grouped by action owner)

  • [ ] @IvanGoncharov - read https://github.com/APIs-guru/graphql-over-http/pull/79 and comment

  • [ ] @jaydenseric - add operationName tests

  • [x] @jaydenseric Continue implementing some of the automated tests in: https://github.com/jaydenseric/graphql-http-test

  • [ ] @jaydenseric (when/if ready this month) open an issue on express-graphql for adding the test/audit suite

  • [x] @sjparsons Share some stats on how common application/graphql is from Braintree and other sources if possible.

    Finding: Braintree's GraphQL API requires application/json currently.

  • [x] @sjparsons Follow up with Brian, Ivan and others from the GraphQL Foundation to get momentum on the technical transfer of the repo.

    Emailed on June 30

  • [ ] @sjparsons Research some other serialization formats and whether they have implications for content-types / status codes.

  • [ ] @sjparsons Document the agreement that we should require MIME-type, making all existing servers non-compliant. Update the intention of the 1.0 release to reflect the new approach to the spec.

  • [ ] @sjparsons Begin file to document the pre-spec state and adoption guide. Include draft structure and preamble

  • [ ] @sjparsons How can the server recognize the client sent a GraphQL Request? Clarify that part in the spec.

  • [x] @spawnia - reflect feedback from meeting in: https://github.com/APIs-guru/graphql-over-http/pull/94

  • [x] @spawnia - reflect feedback from meeting in: https://github.com/APIs-guru/graphql-over-http/pull/79

closed time in 8 days

sjparsons

issue commentAPIs-guru/graphql-over-http

Actions from 2020-05-26 meeting

We're taking a slight different strategy with actions from our meetings and just representing them as Github issues. I've taken the incomplete tasks from this issue and made issues for them for us to track. I've also added Milestones corresponding with meetings + one for the 1.0 release and one for the post-1.0 release.

sjparsons

comment created time in 8 days

issue openedAPIs-guru/graphql-over-http

How to identify GraphQL requests

How can the server recognize the client sent a GraphQL Request? Clarify that part in the spec.

created time in 8 days

issue openedAPIs-guru/graphql-over-http

Pre-spec state and adoption guide

We would like to have a pre-spec state and an adoption guide to be release with the 1.0 version of the spec. We'll be releasing some breaking changes and we want to make it clear what implementors will need to do to become compliant.

Tasks:

  • Begin file to document the pre-spec state and adoption guide. Include draft structure and preamble
  • ... brainstorm how to make this a reality

created time in 8 days

issue openedAPIs-guru/graphql-over-http

Make GraphQL MIME-type required

Document the agreement that we should require MIME-type, making all existing servers non-compliant. Update the intention of the 1.0 release to reflect the new approach to the spec.

created time in 8 days

issue commentAPIs-guru/graphql-over-http

Migration to GraphQL Foundation

Status: We have a tentative green light to do our work under the coverage of the GraphQL foundation:

Hi Sam,

Sorry for the delay. I talked this over with legal, and they suggested that this can be done under the existing graphql spec. This is likely the best outcome, because it means there don't need to be multiple docs and signatures to participate; existing participants would be covered under their existing agreement.

I think from that perspective, the next step is to begin work. Does that make sense?

Best, Brian

I'm inquiring whether this implies we have the green light to start migrating the repo into the GraphQL Foundation Github organization.

sjparsons

comment created time in 8 days

issue openedAPIs-guru/graphql-over-http

Migration to GraphQL Foundation

Acceptance Criteria:

  • Official, legal adoption of the in progress GraphQL over HTTP spec into the GraphQL Foundation
  • Migration of the repo into the GraphQL Foundation Github organization

This is a major step for us to make toward the 1.0 release.

This issue will track the status of this work until it's complete.

created time in 8 days

issue openedAPIs-guru/graphql-over-http

Research other serialization formats

Research some other serialization formats and whether they have implications for content-types / status codes. For example, the usual case that we consider is GraphQL over HTTP with JSON as the serialization format. However, there are other serialization formats in use and this may give us insight as to what the constraints need to be support those in addition to JSON in GraphQL over HTTP.

created time in 8 days

issue closedAPIs-guru/graphql-over-http

Would spec also focus on subscriptions?

Subscriptions are usually handled over the websockets but they could also utilize http protocol in situations like:

  • HTTPS connection update using SNI
  • Long polling like implementations

Would the working group consider extending graphql-over-http to include subscriptions over WebSockets ?

closed time in 8 days

wtrocki

issue commentAPIs-guru/graphql-over-http

Would spec also focus on subscriptions?

I'm going to close this issue for now, since I think the question has been answered. Will plan to answer more questions and entertain topics at the working group on this after the 1.0 release.

wtrocki

comment created time in 8 days

issue commentAPIs-guru/graphql-over-http

Find the best time for the GraphQL over HTTP working group

You're right, @benjie. I've updated the link to 2 hour slots covering that same time period. Let me know if that doesn't work.

sjparsons

comment created time in 8 days

issue openedAPIs-guru/graphql-over-http

Find the best time for the GraphQL over HTTP working group

Hello, we'd like to make sure that we're meeting at the best time possible for all folks. If you're interested in participating, please fill out this doodle with the best time for you on the last Tuesday of every month. I've picked July 28 (next day we'll meet) for the poll, but we'll use this time going forward for every last Tuesday of the month.

https://doodle.com/poll/svz8im6nb2ic64v7

@abernix @balshor @benjie @deinok @erikwittern @jaydenseric @michaelstaib @mike-marcacci @mmatsa @sjparsons @spawnia @sungam3r @enisdenjo

created time in 9 days

issue openedAPIs-guru/graphql-over-http

Extend express-graphql with test/audit suite

@jaydenseric Adding this an issue as it's a better primitive for tracking

created time in 9 days

issue openedAPIs-guru/graphql-over-http

Add operationName audit to the graphql-http-test

When GraphQL queries contain more than one operation, then an operationName should be present in the payload body. Need to add an audit for this case.

https://github.com/jaydenseric/graphql-http-test

@jaydenseric I'm adding this an issue here, if you want to also reference an issue on your repo that'd be cool.

created time in 9 days

pull request commentAPIs-guru/graphql-over-http

Added extensions to the graphql request

Can we merge this? It makes sense to me, but I wasn't clear @IvanGoncharov if your comments "I will forbid all other top-level properties" meant that you now do not approve of this PR?

michaelstaib

comment created time in 9 days

pull request commentAPIs-guru/graphql-over-http

Provide clarifications on content type and serialization

I intend to circle back to this and merge this PR before the July meeting.

sjparsons

comment created time in 9 days

pull request commentAPIs-guru/graphql-over-http

Add clarifications regarding HTTP status codes

For documentation

Action from 2020-06-30 meeting:

Split the PR, keeping the minimal agreed upon changes in the original and open new ones for more controversial changes.

spawnia

comment created time in 9 days

issue closedAPIs-guru/graphql-over-http

30 June 2020 - working group meeting

Hello, just opening a discussion to remind interested devs about our working group meeting on Tuesday, June 30th. Please see the agenda and open a PR to add yourself:

https://github.com/APIs-guru/graphql-over-http/blob/master/working-group/agendas/2020-06-30.md

@abernix @balshor @benjie @deinok @erikwittern @jaydenseric @michaelstaib @mike-marcacci @mmatsa @sjparsons @spawnia @sungam3r @enisdenjo @IvanGoncharov

closed time in 9 days

sjparsons

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha 252fec8c26bd7181ff29fba9037fdcc263371e9e

Update 2020-06-30.md

view details

push time in 9 days

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha c2506d2654e5d6191f7f8b8411a2c07a690d8871

Additional agenda items

view details

push time in 9 days

pull request commentAPIs-guru/graphql-over-http

Clarify URL requirements

I figured we can just merge for now and take any future modifications in a future PR.

spawnia

comment created time in 9 days

push eventAPIs-guru/graphql-over-http

Benedikt Franke

commit sha 6d8d585683f27908c74f122ed2ef01152fc021f3

Clarify URL requirements (#94) * Clarify URL requirements * Clients can send all requests to the same endpoint * Address review comments * Use active voice, thanks @ghmcadams Co-authored-by: Gabriel McAdams <ghmcadams@users.noreply.github.com> * Those URLs MAY also be used for other purpose * Incorporate working group feedback: - No promises on subscriptions for now - Introspection determines the schema Co-authored-by: Gabriel McAdams <ghmcadams@users.noreply.github.com>

view details

push time in 9 days

PR merged APIs-guru/graphql-over-http

Clarify URL requirements

Relates to the discussion in https://github.com/APIs-guru/graphql-over-http/issues/91

@ghmcadams @ralfhandl

+25 -8

2 comments

1 changed file

spawnia

pr closed time in 9 days

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha d62fe55d39a17dd23c9c7487a78b60ea79ea28bc

Add action items agenda item

view details

push time in 9 days

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha 232b63781d9cfe3d06c1ab72e012ff5045aa590d

Add zoom and doc links

view details

push time in 9 days

push eventAPIs-guru/graphql-over-http

Jayden Seric

commit sha 178bca49f7e987f63d6d0af81a8d6ad5142acd13

Add Jayden Seric to the 2020-06-30 agenda (#112) Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

push time in 9 days

push eventjaydenseric/graphql-over-http

mmatsa

commit sha 3e9a6f621cfb03ffba63b73c4dc8db52565e276d

Update 2020-06-30.md (#111) * Update 2020-06-30.md * ordered by org alphabetically Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

Sam Parsons

commit sha 4dc626013c1995d01652b436f5d26b7c70443240

Merge branch 'master' into patch-2

view details

push time in 9 days

push eventAPIs-guru/graphql-over-http

mmatsa

commit sha 3e9a6f621cfb03ffba63b73c4dc8db52565e276d

Update 2020-06-30.md (#111) * Update 2020-06-30.md * ordered by org alphabetically Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

push time in 9 days

push eventmmatsa/graphql-over-http

Sam Parsons

commit sha be2c4d520cb8f69f63a850acea9ace82c7bf98c7

ordered by org alphabetically

view details

push time in 9 days

push eventAPIs-guru/graphql-over-http

Denis Badurina

commit sha f1e8a680a9f7846068c4c40adf3007474a3a3ea5

Add myself to working group (#107) Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

push time in 9 days

PR merged APIs-guru/graphql-over-http

Add myself to working group

Hey, even though I have no agenda, yet, I'd like to attend the Working Group.

+1 -0

1 comment

1 changed file

enisdenjo

pr closed time in 9 days

pull request commentAPIs-guru/graphql-over-http

Add myself to working group

Great to have you join!

enisdenjo

comment created time in 9 days

push eventenisdenjo/graphql-over-http

Benjie Gillam

commit sha 2db7dea6603e655c9eac0824252b00e1a7f0f82d

Add Benjie to June WG (#110)

view details

Michael Staib

commit sha 860083d267216a23be1c9661228da3ac8c15fb45

Added myself to the meeting (#109) Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

Gabriel McAdams

commit sha 9e64ac85314ffde98a7338d798afd8f5298c3efb

Add Gabriel McAdams to the list of attendees (#108) Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

Sam Parsons

commit sha baa8b0a7797f1020e6499451c472540819da1f99

Merge branch 'master' into patch-2

view details

push time in 9 days

push eventAPIs-guru/graphql-over-http

Gabriel McAdams

commit sha 9e64ac85314ffde98a7338d798afd8f5298c3efb

Add Gabriel McAdams to the list of attendees (#108) Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

push time in 9 days

push eventghmcadams/graphql-over-http

Benjie Gillam

commit sha 2db7dea6603e655c9eac0824252b00e1a7f0f82d

Add Benjie to June WG (#110)

view details

Michael Staib

commit sha 860083d267216a23be1c9661228da3ac8c15fb45

Added myself to the meeting (#109) Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

Sam Parsons

commit sha 1ff78ee5060bae7dfb8bce5ba834e92432c2ca10

Merge branch 'master' into master

view details

push time in 9 days

push eventAPIs-guru/graphql-over-http

Michael Staib

commit sha 860083d267216a23be1c9661228da3ac8c15fb45

Added myself to the meeting (#109) Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

push time in 9 days

push eventmichaelstaib/graphql-over-http

Benjie Gillam

commit sha 2db7dea6603e655c9eac0824252b00e1a7f0f82d

Add Benjie to June WG (#110)

view details

Sam Parsons

commit sha f3f2ffc5ba8c116fb5b57daff7636f82741a2895

Merge branch 'master' into patch-7

view details

push time in 9 days

push eventAPIs-guru/graphql-over-http

Benjie Gillam

commit sha 2db7dea6603e655c9eac0824252b00e1a7f0f82d

Add Benjie to June WG (#110)

view details

push time in 9 days

PR merged APIs-guru/graphql-over-http

Add Benjie to June WG

Sorry for lateness, missed this (just saw it in Slack).

+1 -0

0 comment

1 changed file

benjie

pr closed time in 9 days

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha fe1f4682e9f6170cdad69cece94297e67bb155f6

Add slack link to README

view details

push time in 10 days

issue openedAPIs-guru/graphql-over-http

30 June 2020 - working group meeting

Hello, just opening a discussion to remind interested devs about our working group meeting on Tuesday, June 30th. Please see the agenda and open a PR to add yourself:

https://github.com/APIs-guru/graphql-over-http/blob/master/working-group/agendas/2020-06-30.md

@abernix @balshor @benjie @deinok @erikwittern @jaydenseric @michaelstaib @mike-marcacci @mmatsa @sjparsons @spawnia @sungam3r @enisdenjo @IvanGoncharov

created time in 10 days

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha 81d7047d77ca61347518b4a7d9ae025e4f6643dc

Add @enisdenjo to CC helper

view details

push time in 10 days

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha f0c1523744dd89cdc321200b9047e94b84b07f2b

Add @enisdenjo to CC helpder

view details

push time in 10 days

push eventAPIs-guru/graphql-over-http

Benedikt Franke

commit sha 96b86fa5bb8e73a0f5a9177886a2087b96f9c3ee

Add myself and PR reviews to agenda (#105)

view details

push time in 10 days

pull request commentAPIs-guru/graphql-over-http

Add myself and PR reviews to agenda

Thanks Benedikt! See you tomorrow

spawnia

comment created time in 10 days

push eventAPIs-guru/graphql-over-http

Denis Badurina

commit sha d107b5e83bd78452cc65f73563d20be0d91d4138

Add @enisdenjo to list of interested developers (#104)

view details

push time in 10 days

PR merged APIs-guru/graphql-over-http

Add @enisdenjo to list of interested developers

👋

I am interested in contributing to the GQL spec, more specifically in the area of subscriptions. Contradictory to subscriptions-transport-ws being slowly abandoned, the need for realtime is blooming! Nevertheless, their 3-year-old GraphQL over WebSocket Protocol is very relevant and highly used.

Lets splash some modern water on it and standardise it!

+3 -0

1 comment

1 changed file

enisdenjo

pr closed time in 10 days

pull request commentAPIs-guru/graphql-over-http

Add @enisdenjo to list of interested developers

Thanks for your interest! We'll be meeting tomorrow.

I will say that standardizing subscriptions is something we want to entertain after we get the 1.0 release out. You can see the ROADMAP for some of our thinking of what needs to be in the 1.0 release.

enisdenjo

comment created time in 10 days

delete branch sjparsons/custom-actions-docs

delete branch : minor-improvements

delete time in a month

issue closedbraintree/custom-actions-docs

Broken links to reference

I found some broken links, but I don't know how to fix them since I'm not sure where they should point. I added a branch in my fork that changes the target to BAD_LINK just to identify them. Seeking input on where to point them to.

https://github.com/braintree/custom-actions-docs/compare/master...sjparsons:fix-broken-link

closed time in a month

sjparsons

issue commentbraintree/custom-actions-docs

Broken links to reference

I removed the broken links in gitbook, so closing the issue now.

sjparsons

comment created time in a month

push eventsjparsons/custom-actions-docs

Sam Parsons

commit sha c11dded3cb3897e7bc0ebd71db3a4112dc5c4c84

Remove links

view details

push time in a month

Pull request review commentbraintree/custom-actions-docs

Update examples to help first-timers

 mutation ExampleAuth($input: AuthorizePaymentMethodInput!) {   "input": {     "paymentMethodId": "tokencap_123",     "transaction": {+      "merchantAccountId": "id_of_custom_action_enabled_merchant_account",

Maybe we could add some text like this:

If your default merchant account has custom actions enabled, then you don't need to specify merchantAccountId.

sjparsons

comment created time in a month

issue openedbraintree/custom-actions-docs

Broken links to reference

I found some broken links, but I don't know how to fix them since I'm not sure where they should point. I added a branch in my fork that changes the target to BAD_LINK just to identify them.

https://github.com/braintree/custom-actions-docs/compare/master...sjparsons:fix-broken-link

created time in a month

push eventsjparsons/custom-actions-docs

Sam Parsons

commit sha 9b5a35fbc8fa5a40f378a5021a756664582fa295

Identify broken links

view details

push time in a month

create barnchsjparsons/custom-actions-docs

branch : fix-broken-link

created branch time in a month

PR opened braintree/custom-actions-docs

Update examples to help first-timers

This PR provides a couple of improvements to make some examples work right away out-of-the-box.

  1. In the example on Invoking the Authorization handler: include a merchantAccountId attribute. My default merchant account did not have did not have custom actions enabled and so I had to make this modification.
  2. In the example on Tokenization:
  • Add an id to the tokenzize GraphQL mutation so that it's returned in the response since it's needed in downstream requests.
  • Update the actionName in the customActionsPaymentMethod input to match case with the created custom actions project that was deployed. I had to make the case match between project and the actionName in order to get successful authorizations.
+4 -2

0 comment

1 changed file

pr created time in a month

push eventsjparsons/custom-actions-docs

Sam Parsons

commit sha 51c53dae90c7e7f4187e5700ba9785a35610ee34

Add id and merchantAccountId

view details

push time in a month

create barnchsjparsons/custom-actions-docs

branch : minor-improvements

created branch time in a month

pull request commentbraintreeps/vim_dotfiles

Automatically format terraform *.tfvars files on save

In response to feedback from other devs, I've altered this PR to use ALE to do the fixes that we need.

sjparsons

comment created time in a month

push eventsjparsons/vim_dotfiles

Sam Parsons

commit sha d129589fc6b9de297a39a8c3d215a5c003bc2864

Use ALE to autoformat terraform files

view details

push time in a month

issue closedAPIs-guru/graphql-over-http

Actions from 24 April 2020 meeting

Sorry, I'm a bit late in posting this... Based on the 24 April 2020 working meeting, here's the planned actions we'd like to work on next. If you're tagged here and you feel you cannot meet that commitment, please comment or DM me. Also, if you'd like to get involved on any of these actions just post.

Planned before next meeting:

  • [ ] @sjparsons Research some other serialization formats and whether they have implications for content-types / status codes.
  • [x] @sjparsons Merge proposed automated tests https://github.com/APIs-guru/graphql-over-http/pull/75
  • [ ] @jaydenseric (pending above) Implement some of the automated tests in: https://github.com/jaydenseric/graphql-http-test
  • [ ] @michaelstaib How many other people are using application/graphql as a common format instead of application/graphql+json for submitting requests. GitHub? Shopify? Braintree (@sjparsons can look into this) How popular is it?
  • [ ] @sjparsons How can the server recognize the client sent a GraphQL Request? Clarify that part in the spec.

closed time in a month

sjparsons

issue commentAPIs-guru/graphql-over-http

Actions from 24 April 2020 meeting

Closing in preference of https://github.com/APIs-guru/graphql-over-http/issues/103

sjparsons

comment created time in a month

issue openedAPIs-guru/graphql-over-http

Actions from 2020-05-26 meeting

Based on the 2020-05-26 working group meeting, here's the planned actions we'd like to work on next. If you're tagged here and you feel you cannot meet that commitment, please comment or DM me. Also, if you'd like to get involved on any of these actions just post.

(grouped by action owner)

  • [ ] @IvanGoncharov - read https://github.com/APIs-guru/graphql-over-http/pull/79 and comment

  • [ ] @jaydenseric - add operationName tests

  • [ ] @jaydenseric Continue implementing some of the automated tests in: https://github.com/jaydenseric/graphql-http-test

  • [ ] @jaydenseric (when/if ready this month) open an issue on express-graphql for adding the test/audit suite

  • [ ] @sjparsons Research some other serialization formats and whether they have implications for content-types / status codes.

  • [ ] @sjparsons Share some stats on how common application/graphql is from Braintree and other sources if possible.

  • [ ] @sjparsons How can the server recognize the client sent a GraphQL Request? Clarify that part in the spec.

  • [ ] @sjparsons Follow up with Brian, Ivan and others from the GraphQL Foundation to get momentum on the technical transfer of the repo.

  • [ ] @sjparsons Document the agreement that we should require MIME-type, making all existing servers non-compliant. Update the intention of the 1.0 release to reflect the new approach to the spec.

  • [ ] @sjparsons Begin file to document the pre-spec state and adoption guide. Include draft structure and preamble

  • [ ] @spawnia - reflect feedback from meeting in: https://github.com/APIs-guru/graphql-over-http/pull/94

  • [ ] @spawnia - reflect feedback from meeting in: https://github.com/APIs-guru/graphql-over-http/pull/79

created time in a month

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha 59028bd1cf17896c930d936a10fba228982ed310

Rename 2020-06-30 to 2020-06-30.md

view details

push time in a month

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha 0a36fadb8a67178b908b051bcbb4e33015816399

Create June agenda

view details

push time in a month

issue closedAPIs-guru/graphql-over-http

26 May 2020 - working group meeting

Hello, just opening a discussion to remind interested devs about our working group meeting on Tuesday, May 26th. Please see the agenda and open a PR to add yourself:

https://github.com/APIs-guru/graphql-over-http/blob/master/working-group/agendas/2020-05-26.md

@abernix @balshor @benjie @deinok @ErikWittern @jaydenseric @michaelstaib @mike-marcacci @mmatsa @sjparsons @spawnia @sungam3r @IvanGoncharov

closed time in a month

sjparsons

push eventAPIs-guru/graphql-over-http

Benedikt Franke

commit sha 6129b91aef33440a496b444cce98477027e6839c

Discuss PRs in agenda (#102)

view details

push time in a month

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha 51a73512699f724180056110a9342d6578411c88

Update to GraphQL foundation zoom link

view details

push time in a month

push eventAPIs-guru/graphql-over-http

mmatsa

commit sha 9ea60f7e29cbd2fc0f6487b7fad501a6a0ff8c1c

Add myself to attendee list (#101)

view details

push time in a month

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha 617598f1a27ed69d004a00f16a42ccd36f0f0b6b

Add zoom link for 2020-05-26

view details

push time in a month

push eventAPIs-guru/graphql-over-http

Jayden Seric

commit sha ede567c89a521e9ad9f8ded21b1c25c6242b9da1

Add Jayden Seric to the 2020-05-26 attendees (#100) * Add Jayden Seric to the 2020-05-26 attendees * Restore the other attendees. Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

push time in a month

push eventjaydenseric/graphql-over-http

Sam Parsons

commit sha be7174a5bd8faadf7130d9508f043e4681ab986e

Add google doc link, and agenda items

view details

Sam Parsons

commit sha 018f083e4a7bbf22a6f42f2ca5651dfc19e304cf

Merge branch 'master' into patch-1

view details

push time in a month

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha be7174a5bd8faadf7130d9508f043e4681ab986e

Add google doc link, and agenda items

view details

push time in a month

push eventAPIs-guru/graphql-over-http

Benjie Gillam

commit sha 639f5957fd20776b803b6afd81bcd29b83e46516

Add Benjie to May WG (#99)

view details

push time in a month

PR merged APIs-guru/graphql-over-http

Add Benjie to May WG

Sorry for the late addition!

+1 -0

0 comment

1 changed file

benjie

pr closed time in a month

push eventAPIs-guru/graphql-over-http

Gabriel McAdams

commit sha 8b8373c0f5ef1422bbdf1509dd556e898f7e9310

Add Gabriel McAdams to the May meeting attendees list (#98) Co-authored-by: Sam Parsons <sjparsons@gmail.com>

view details

push time in a month

push eventghmcadams/graphql-over-http

Benedikt Franke

commit sha 0203b80cb66d6ffb1187b448ba8ba79056642949

Add Benedikt to May's agenda (#97)

view details

Sam Parsons

commit sha 3dfe222a1955dffa34071dfc2f6ec5d3ce5934a3

Merge branch 'master' into master

view details

push time in a month

push eventAPIs-guru/graphql-over-http

Benedikt Franke

commit sha 0203b80cb66d6ffb1187b448ba8ba79056642949

Add Benedikt to May's agenda (#97)

view details

push time in a month

issue commentAPIs-guru/graphql-over-http

Actions from 24 April 2020 meeting

@jaydenseric I merged https://github.com/APIs-guru/graphql-over-http/blob/master/working-group/test-suite.md so that should unblock you, though I know there's not much time before next meeting.

sjparsons

comment created time in 2 months

delete branch APIs-guru/graphql-over-http

delete branch : test-suite

delete time in 2 months

push eventAPIs-guru/graphql-over-http

Sam Parsons

commit sha d078a94198132dc185cbcc5528f77c79072b1042

Tests to build (#75) * First draft of test suite * Updates * Address review comments

view details

push time in 2 months

more