profile
viewpoint
Lee Byron leebyron San Francisco leebyron.com I make things @robinhood, previously @facebook.

immutable-js/immutable-js 30041

Immutable persistent data collections for Javascript which increase efficiency and simplicity.

graphql/graphql-js 16508

A reference implementation of GraphQL for JavaScript

graphql/graphql-spec 12836

GraphQL is a query language and execution engine tied to any backend service.

chentsulin/awesome-graphql 11773

Awesome list of GraphQL & Relay

graphql/graphql.github.io 557

GraphQL Documentation at graphql.org

leebyron/async-to-gen 508

⌛ Use async functions in your JavaScript today with speed and simplicity.

graphql/graphql-wg 254

Working group notes for GraphQL

leebyron/cocoa-oauth2 58

Cocoa library for handling oauth2

graphql/faq 35

GraphQL FAQ

leebyron/anyconnect-dark 20

Dark OSX menu bar assets for Cisco AnyConnect VPN.

push eventgraphql/graphql-wg

Robert Zhu

commit sha 36001f27b921c22cfd23761d1557e4c776e24f69

Update 2020-07-02.md (#449) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

push time in 20 days

PR merged graphql/graphql-wg

Update 2020-07-02.md
+1 -0

0 comment

1 changed file

robzhu

pr closed time in 20 days

push eventrobzhu/graphql-wg

Lee Byron

commit sha 413deb6620c2843a711edc2f5237a82a0793e609

Update 2020-07-02.md

view details

Tejas Dinkar

commit sha b3bfff3210e913bb43d64952a655265894d035c2

Update 2020-07-02.md (#450) * Update 2020-07-02.md * Update 2020-07-02.md

view details

Lee Byron

commit sha 620c5b717ab3bde93718635dd14a944cd37980d4

Merge branch 'master' into patch-11

view details

push time in 20 days

push eventgraphql/graphql-wg

Tejas Dinkar

commit sha b3bfff3210e913bb43d64952a655265894d035c2

Update 2020-07-02.md (#450) * Update 2020-07-02.md * Update 2020-07-02.md

view details

push time in 20 days

PR merged graphql/graphql-wg

Update 2020-07-02.md
+1 -0

0 comment

1 changed file

gja

pr closed time in 20 days

push eventgraphql/graphql-spec

Travis CI

commit sha 61df69f16ec88cd0bc537a607aa9e5d7c73a2111

Deploy to GitHub Pages

view details

push time in 20 days

push eventgraphql/graphql.github.io

Travis CI

commit sha 122b0ac37155a97283ebc0f1339a2acaf6c80a2d

Auto-deploy by Travis CI

view details

push time in 23 days

push eventgraphql/graphql.github.io

Travis CI

commit sha bd44d1c5a4c5727009cd8bf2dee1fce888096279

Auto-deploy by Travis CI

view details

push time in 23 days

push eventgraphql/graphql.github.io

Travis CI

commit sha b0f6e2829e832b4c880f658d56af46ea509d1e4a

Auto-deploy by Travis CI

view details

push time in 23 days

issue commentgraphql/graphql.github.io

Proposal - Migrating the website to Gatsby/Next.js

Does it make sense to do this work on a branch in this repo instead of a fork?

On Mon, Jul 6, 2020 at 7:15 PM ਸਹਜਪ੍ਰੀਤ ਸਿੰਘ notifications@github.com wrote:

I have started a fork https://github.com/saihaj/graphql.github.io if anyone is interested we can work together, contact me on GraphQL slack, email me or open up an issue in the fork. It can be previewed here -> https://graphql-docs-gatsby.vercel.app/

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/graphql/graphql.github.io/issues/875#issuecomment-654557589, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAMHUS4SBPQRKTJ63WXSYLR2KAMXANCNFSM4NRURGVA .

-- Lee Byron

Urigo

comment created time in a month

pull request commentgraphql/graphql-spec

Add to the @deprecated directive to allow deprecation of inputValues

Capturing discussion notes from WG meeting:

There is one remaining pitfall from this change, and that's deprecating a required argument or input field. There are two problems with this:

  1. Deprecations are intended to be actionable: a client should be able to edit queries to contain no deprecated elements. It would not be possible to remove a deprecated required argument.

  2. Introspection does not include deprecated portions of the schema by default, you must pass (includeDeprecated: true) to the relevant potion. This could result in a scenario where a client omits the deprecated portion of a schema from introspection and therefore does not know about an required argument. What appears valid during client development is rejected as invalid by the service, a surprising outcome. Note that this is not an abstract concern since no current tool asks for deprecated arguments or input fields and so all current tools could suffer this scenario.

The recommended addition to finalize this spec proposal (and linked PR) is to include a schema validation rule whereby any deprecated argument or input field is not also required. There is an open question whether this should be a "must" or a "should" rule, which @eapache will help investigate - either way the reference implementation GraphQL.js will include this schema validation rule.

smitt04

comment created time in a month

push eventgraphql/graphql-spec

Travis CI

commit sha af043c433c22534152fd2c072943f5cff577cac3

Deploy to GitHub Pages

view details

push time in a month

pull request commentgraphql/graphql-spec

[RFC] Custom Scalar Specification URLs

Notes from meeting:

URL example is a good one, but it would be useful to have an example showing a vendor example.

eapache

comment created time in a month

pull request commentgraphql/graphql-spec

[RFC] Custom Scalar Specification URLs

Will take a careful read-over before merging

eapache

comment created time in a month

push eventgraphql/graphql-wg

Lee Byron

commit sha 413deb6620c2843a711edc2f5237a82a0793e609

Update 2020-07-02.md

view details

push time in a month

Pull request review commentgraphql/graphql-spec

Spec edits for @defer/@stream

 FieldsInSetCanMerge(set):     {set} including visiting fragments and inline fragments.   * Given each pair of members {fieldA} and {fieldB} in {fieldsForName}:     * {SameResponseShape(fieldA, fieldB)} must be true.+    * {SameStreamDirective(fieldA, fieldB)} must be true.

SameStreamAndDeferDirective?

robrichard

comment created time in a month

pull request commentgraphql/graphql-spec

add explanation about argument name uniquess.

Marking this proposal as Stage 1.

Next steps are making sure this has a reflecting PR to the graphql.js reference implementation

dugenkui03

comment created time in a month

push eventgraphql/graphql-wg

Lee Byron

commit sha 8928996310308d5227e80f49ee97a9051daf5024

Update 2020-07-02.md

view details

push time in a month

pull request commentgraphql/graphql-wg

Add Benjie to July 2020 WG

Just added notes!

benjie

comment created time in a month

push eventgraphql/graphql-wg

Benjie Gillam

commit sha e27918ea83d505726e521d3fc371483521df6ece

Add Benjie to July 2020 WG (#448)

view details

push time in a month

PR merged graphql/graphql-wg

Add Benjie to July 2020 WG

Sorry for the late PR - was looking at agenda for the live notes link and realised I hadn't added myself! :facepalm:

+1 -0

0 comment

1 changed file

benjie

pr closed time in a month

push eventgraphql/graphql-wg

Lee Byron

commit sha bc54f93493496b87e656b097ded9285686e50433

Update 2020-07-02.md

view details

push time in a month

delete branch graphql/graphql-wg

delete branch : IvanGoncharov-patch-1

delete time in a month

push eventgraphql/graphql-wg

Ivan Goncharov

commit sha e96b7f590da8e19505a2b5548eb2cbff845e7a89

Add Ivan to July 2020 WG and add agenda item (#447) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

push time in a month

push eventgraphql/graphql-wg

mmatsa

commit sha 3a943356ec5e6ccb72b2c33a39caf86dd26a4838

Update 2020-07-02.md (#446)

view details

Lee Byron

commit sha 4777d6453ac8a2d11978a947aad50d17082b5c46

Merge branch 'master' into IvanGoncharov-patch-1

view details

push time in a month

push eventgraphql/graphql-wg

mmatsa

commit sha 3a943356ec5e6ccb72b2c33a39caf86dd26a4838

Update 2020-07-02.md (#446)

view details

push time in a month

PR merged graphql/graphql-wg

Update 2020-07-02.md
+1 -0

0 comment

1 changed file

mmatsa

pr closed time in a month

push eventgraphql/graphql-wg

Matt Mahoney

commit sha 3087a6d880ed1da35b469d5fa3818639a0996f73

Add Matt Mahoney (#445) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

push time in a month

push eventmjmahone/graphql-wg

Stephen Spalding

commit sha 9de43272c90d75bcb9d7fb2c247bf0748c7068aa

Update 2020-07-02 agenda re: deprecated input fields (#441) Co-authored-by: Stephen Spalding <sspalding@netflix.com>

view details

Andreas Marek

commit sha a678f8e82664e56a3cad90867a314fb845b85d12

Update 2020-07-02.md (#442)

view details

Jesse Rosenberger

commit sha e8f5c6dacef0c8e5bf3255f68bc32421ea43766b

Add Jesse Rosenberger to 2020-07-02 agenda. (#443)

view details

Evan Huus

commit sha 8a822d3b83266093b4d215529cdd3fddc97edb10

Add Evan to July meeting (#444) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

Lee Byron

commit sha 4a159b1d7c0cc1a77459f5d155572721ce5a0f57

Merge branch 'master' into patch-16

view details

push time in a month

push eventgraphql/graphql-wg

Evan Huus

commit sha 8a822d3b83266093b4d215529cdd3fddc97edb10

Add Evan to July meeting (#444) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

push time in a month

PR merged graphql/graphql-wg

Add Evan to July meeting
+1 -0

0 comment

1 changed file

eapache

pr closed time in a month

push eventeapache/graphql-wg

Stephen Spalding

commit sha 9de43272c90d75bcb9d7fb2c247bf0748c7068aa

Update 2020-07-02 agenda re: deprecated input fields (#441) Co-authored-by: Stephen Spalding <sspalding@netflix.com>

view details

Andreas Marek

commit sha a678f8e82664e56a3cad90867a314fb845b85d12

Update 2020-07-02.md (#442)

view details

Jesse Rosenberger

commit sha e8f5c6dacef0c8e5bf3255f68bc32421ea43766b

Add Jesse Rosenberger to 2020-07-02 agenda. (#443)

view details

Lee Byron

commit sha d4138bde625861cfe645a3fa45601bd94cbbca7d

Merge branch 'master' into patch-8

view details

push time in a month

push eventgraphql/graphql-wg

Jesse Rosenberger

commit sha e8f5c6dacef0c8e5bf3255f68bc32421ea43766b

Add Jesse Rosenberger to 2020-07-02 agenda. (#443)

view details

push time in a month

push eventgraphql/graphql-wg

Andreas Marek

commit sha a678f8e82664e56a3cad90867a314fb845b85d12

Update 2020-07-02.md (#442)

view details

push time in a month

PR merged graphql/graphql-wg

add myself and agenda topics
+2 -0

0 comment

1 changed file

andimarek

pr closed time in a month

push eventgraphql/graphql-wg

Stephen Spalding

commit sha 9de43272c90d75bcb9d7fb2c247bf0748c7068aa

Update 2020-07-02 agenda re: deprecated input fields (#441) Co-authored-by: Stephen Spalding <sspalding@netflix.com>

view details

push time in a month

push eventgraphql/graphql-wg

Stephen Spalding

commit sha d3f9344d11d9dcdd6a0cdf319a7e1ff8791e2303

Add Stephen and an agenda item (#440) Co-authored-by: Stephen Spalding <sspalding@netflix.com> Co-authored-by: Lee Byron <lee@leebyron.com>

view details

push time in a month

push eventfotoetienne/graphql-wg

Jason Kuhrt

commit sha 4bb6c1d175255a98faf856f0b2d90d20454282cc

Update 2020-07-02.md (#437)

view details

Michael Staib

commit sha 47e3f785b5945fcd1602f6f72e48b45256fbf38d

Added Michael Staib to the meeting (#438) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

Rob Richard

commit sha 5639b9a4e6e86370e0dec8b015d5b7d4e9899240

Update 2020-07-02.md (#439) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

Lee Byron

commit sha 525ee6681e98ad5b56f2000a9f751b2928756fbf

Merge branch 'master' into 2020-07-02

view details

push time in a month

push eventgraphql/graphql-wg

Rob Richard

commit sha 5639b9a4e6e86370e0dec8b015d5b7d4e9899240

Update 2020-07-02.md (#439) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

push time in a month

push eventrobrichard/graphql-wg

Jason Kuhrt

commit sha 4bb6c1d175255a98faf856f0b2d90d20454282cc

Update 2020-07-02.md (#437)

view details

Michael Staib

commit sha 47e3f785b5945fcd1602f6f72e48b45256fbf38d

Added Michael Staib to the meeting (#438) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

Lee Byron

commit sha 1afc5ff9b0f29cb48bda26543ff769354f2d3777

Merge branch 'master' into patch-4

view details

push time in a month

push eventgraphql/graphql-wg

Michael Staib

commit sha 47e3f785b5945fcd1602f6f72e48b45256fbf38d

Added Michael Staib to the meeting (#438) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

push time in a month

push eventmichaelstaib/graphql-wg

Jason Kuhrt

commit sha 4bb6c1d175255a98faf856f0b2d90d20454282cc

Update 2020-07-02.md (#437)

view details

Lee Byron

commit sha e1462b9b7116f5682985ea5c0b270caf15951e8c

Merge branch 'master' into patch-7

view details

push time in a month

push eventgraphql/graphql-wg

Jason Kuhrt

commit sha 4bb6c1d175255a98faf856f0b2d90d20454282cc

Update 2020-07-02.md (#437)

view details

push time in a month

issue commenttc39/proposal-iterator-helpers

Iterator.from is inconsistent with Array.from and proposed Set.from

I'd stop short of claiming that ecmascript is intuitive (lol) but I'd claim this has less to do with naming intuition and more to do with system wide consistency.

Constructor(x) not always producing a new instance is a long existing pattern that goes back to the early versions of JS with String(), Number(), Boolean() and Object() coercion functions and returning the same value if that value is of that type, while calling with new produce new instances.

Though even here ECMAScript is not always consistent. Array() does always produce new arrays. In fact the original motivation for introducing Array.from() was because the Array() logic was confusing and hard to control or type check (https://www.ecma-international.org/ecma-262/11.0/#sec-array-len), the existing functionality couldn't be changed for compatibility reasons so Array.from() and Array.of were introduced as workarounds to construct new Arrays with more predictable logic.

My understanding is that the motivation to propose adding Set.from and Map.from stem from similar problems. The Set and Map constructors are not callable as functions (only as new'd constructors) and therefore are difficult to pass around in functional style code. Again, can't reasonably change the functions because of compatibility issues, so that proposal mirror's Array's methods including the use of mapFn and thisArg.

If it were up to me, I'd avoid the whole mapFn construction pattern altogether that Iterator.from() implies by name (if that name was chosen to mirror Array.from)

Something I've tried to avoid in this proposal is having people interact with Iterator as a function, in much the same way you shouldn't really ever directly interact with %TypedArray%.

This is really interesting and makes sense given that it's an abstract class and you can't construct one directly. I can see a similar argument made for Iterator - that's not really even an abstract class, it's just an interface pattern you can implement by providing the right methods. I can see x instanceof Iterator becoming a potentially problematic pattern - could work most of the time for %ArrayIterator% and other built-ins, but not working for custom iterators. If the goal is to avoid interacting with Iterator as a function, perhaps it shouldn't be one at all?

Perhaps:

Iterator.create({ 
  next() {...}
})

Instead of Object.setPrototypeOf(MyIteratorPrototype, Iterator.prototype)?

shicks

comment created time in a month

issue commenttc39/proposal-iterator-helpers

Iterator.from is inconsistent with Array.from and proposed Set.from

I believe the origin of this expectation comes from Array.from

  • https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/from
    • "creates a new, shallow-copied Array instance"

The spec itself doesn't mention this, nor does the proposal to add .from to more types (https://github.com/tc39/proposal-setmap-offrom) though in all those cases they do in fact construct new types (and use a provided mapFn and thisArg to do so)

shicks

comment created time in a month

issue commenttc39/proposal-iterator-helpers

Iterator.from is inconsistent with Array.from and proposed Set.from

Either way I think we should define the behavior of calling Iterator if it's going to be available as a global variable. Array and Object can be called as coercion functions as you describe above. Map and Set can be called with new to construct new instances.

For Iterator, constructing new instances doesn't make sense, so calling with new should probably throw.

shicks

comment created time in a month

issue commenttc39/proposal-iterator-helpers

Iterator.from is inconsistent with Array.from and proposed Set.from

Thanks for readdressing this one. I was pretty terse with that feedback in #48 but I completely agree with your analysis, my original intention with my proto proposal was for it to behave as a coercion function and not a remapping or creation function

You can see that in my implementation here https://github.com/leebyron/ecmascript-iterator-hof/blob/master/polyfill-spec.js#L5

shicks

comment created time in a month

MemberEvent

issue commentgraphql/graphql-scalars

URL Proposal

Up for discussion @graphql/graphql-scalars

leebyron

comment created time in a month

issue openedgraphql/graphql-scalars

URL Proposal

Here's my pitch for how the built URLs could work:

Urls follow a /namespace/scalar/version hierarchy:

  • https://scalars.graphql.org/
    • Lists out all scalars plus a search box
  • https://scalars.graphql.org/namespace/
    • Lists out all scalars within a namespace.
    • Namespaces are required to be github usernames or orgs so we can render a link that replaces "scalars.graphql.org" with "github.com" and takes you somewhere useful.
  • https://scalars.graphql.org/namespace/scalar
    • Metadata about a scalar spec including usage numbers (if we can get those, cdn hits API?) and links to all published versions (similar to https://spec.graphql.org/ ?)
    • Note that the scalar name in a URL is non-normative. It does not affect the name of the scalar found in someone's schema.
  • https://scalars.graphql.org/namespace/scalar/vA.B.C
    • Loads a specific version of a scalar spec. This URL is immutable
  • https://scalars.graphql.org/namespace/scalar/vA
    • Loads latest version which matches vA.X.X (this could be a 302 redirect)
  • https://scalars.graphql.org/namespace/scalar/vA.B
    • Loads latest version which matches vA.B.X (this could be a 302 redirect)

Examples:

  • https://scalars.graphql.org/andimarek/datetime/v1.0.0
    • Andi's original datetime proposal
  • https://scalars.graphql.org/graphql/url/v2.0.12
    • A future official URL scalar type

Semver rules:

  • Major (vA.X.X)
    • Any change which is not backwards compatible with previous scalar specs
    • Example: a serialization format has changed
  • Minor (vX.B.X)
    • Any behavioral change which is backwards compatible
    • Example: an input validation rule was made more lenient
  • Patch (vX.X.C)
    • Non-behavioral changes
    • Example: Copy edits or additional examples

Implementation:

  • Current version is added to the top of the scalar spec markdown file as front-matter
  • This is always in the form vA.B to avoid merge conflicts for every PR.
    • The webpage generator should pick the next highest digit to create a vA.B.C from any previous built page if the frontmatter version does not change in a merged PR.
  • Part of our template guidelines should include semver guidelines. PRs that include behavioral changes should be encouraged to update the version front-matter as part of their patch.

created time in a month

created repositorygraphql/graphql-scalars

created time in a month

push eventgraphql/graphql-spec

Travis CI

commit sha 3c56b81291bd8d721d5e90ea43fda3866dd31660

Deploy to GitHub Pages

view details

push time in a month

push eventgraphql/graphql.github.io

Travis CI

commit sha fda3a41382cebde5fe330d6ec24bc7728805db7c

Auto-deploy by Travis CI

view details

push time in a month

push eventgraphql/graphql.github.io

Travis CI

commit sha 9f1d192a607f70d657ef10ac872ee945c6419d3b

Auto-deploy by Travis CI

view details

push time in a month

push eventgraphql/graphql.github.io

Travis CI

commit sha e486c51c2739dfce18167423f4acc31fe0327071

Auto-deploy by Travis CI

view details

push time in a month

push eventgraphql/graphql.github.io

Travis CI

commit sha 0e866ad7a72f60a1ad8017fd15f7622043bc8fc7

Auto-deploy by Travis CI

view details

push time in a month

push eventgraphql/graphql-spec

Travis CI

commit sha f305ba76ad3842b3e751b0792b06b88e8fddacb3

Deploy to GitHub Pages

view details

push time in a month

pull request commentgraphql/graphql-wg

Add Jesse Rosenberger to 2020-06-11 agenda.

Thanks for following up sorry for the late merge. Your read on alpha sort is correct. I usually try to take a pass before the meeting starts

abernix

comment created time in 2 months

push eventgraphql/graphql-wg

Jesse Rosenberger

commit sha 53fa9bdb9a545ddbe46ed591194dcac44de35343

Add Jesse Rosenberger to 2020-06-11 agenda. (#435)

view details

push time in 2 months

PR merged graphql/graphql-wg

Add Jesse Rosenberger to 2020-06-11 agenda.

I don't quite know what the policy is for ordering of attendee names in this list. I thought at one point it was roughly alphabetically by company after individual contributors and foundation members, but not sure what the best pattern is anymore and not sure who individual contributors are / felt weird putting myself at the top of the list. 😄

Therefore, I'm going for least likely chance of a GitHub merge conflict based on existing PRs for the same file that are currently open.

+1 -0

0 comment

1 changed file

abernix

pr closed time in 2 months

push eventgraphql/graphql-spec

Travis CI

commit sha edce937442a65330cb2ce63b8729fd92a5f60b5a

Deploy to GitHub Pages

view details

push time in 2 months

push eventgraphql/graphql-spec

Travis CI

commit sha 6b9f177ac1cf5a6870376b35799714f614b14ef1

Deploy to GitHub Pages

view details

push time in 2 months

push eventgraphql/graphql-spec

Travis CI

commit sha 21e7ff49cd0229b198b165cc554332d12dd61368

Deploy to GitHub Pages

view details

push time in 2 months

push eventgraphql/graphql-wg

Trevor Scheer

commit sha 6d04b2993c6a97f0a70a6a3ae5d7ee0430828203

Add Trevor Scheer to attendees list (#434)

view details

push time in 2 months

issue closedgraphql/graphql-wg

[2020-05-07] Include defer/stream problem statements in RFC doc

https://github.com/graphql/graphql-wg/blame/master/notes/2020-05-07.md#L168

closed time in 2 months

leebyron

push eventgraphql/graphql-wg

Lee Byron

commit sha 46c5f2206ddb058e5c5d75f1b0917d42e380205a

remove prompt

view details

push time in 2 months

push eventgraphql/graphql-wg

Gabriel McAdams

commit sha cc38b49cf8cf6ddcb1335b515ffc20d9cc5feb1e

Add Gabriel McAdams to the list of attendees (#433)

view details

push time in 2 months

push eventgraphql/graphql-wg

Lee Byron

commit sha b2917135531ef03b0ef718511dd8794ebad1e55d

remove prompts

view details

push time in 2 months

push eventgraphql/graphql-wg

Lee Byron

commit sha 9073bd59d9b2495159614173343c421d4373d30b

notes, sort, formatting

view details

push time in 2 months

push eventgraphql/graphql-wg

Rikki Schulte

commit sha c41a15efca660af13634f0504d08b16c4f788926

add Rikki to attendees (#431) Co-authored-by: Lee Byron <lee@leebyron.com>

view details

push time in 2 months

PR merged graphql/graphql-wg

add Rikki to attendees
+1 -0

0 comment

1 changed file

acao

pr closed time in 2 months

push eventacao/graphql-wg

Vince Foley

commit sha 3f5b13095399f5626a784128afc9f7653d5b4ef9

Add vince (#432)

view details

Lee Byron

commit sha 269f07e0922078c2f485d645ec9d82d5efc89598

Merge branch 'master' into patch-4

view details

push time in 2 months

push eventgraphql/graphql-wg

Vince Foley

commit sha 3f5b13095399f5626a784128afc9f7653d5b4ef9

Add vince (#432)

view details

push time in 2 months

PR merged graphql/graphql-wg

Add vince

@leebyron

+1 -0

0 comment

1 changed file

binaryseed

pr closed time in 2 months

delete branch graphql/graphql-wg

delete branch : IvanGoncharov-patch-1

delete time in 2 months

push eventgraphql/graphql-wg

Ivan Goncharov

commit sha 05a765c70096389d1e5a30bf89dc09b30f27cc3a

Update 2020-06-11.md (#430)

view details

push time in 2 months

push eventgraphql/graphql-wg

Alan Cha

commit sha 5676e28c792973f3df7c10992455c70537dee755

Add Alan Cha to attendees (#429)

view details

push time in 2 months

PR merged graphql/graphql-wg

Add Alan Cha to attendees
+1 -0

0 comment

1 changed file

Alan-Cha

pr closed time in 2 months

issue commentgraphql/graphql-wg

Schedule working session with Input Union RFC champions

Closing this since we scheduled and met!

binaryseed

comment created time in 2 months

issue closedgraphql/graphql-wg

Schedule working session with Input Union RFC champions

Our next step in the Input Union RFC process is to gather the individual solution champions for a working session where we can dive into the details of solutions and try to make some progress towards a proposed solution.

  • https://github.com/graphql/graphql-spec/blob/master/rfcs/InputUnion.md

Our aim is to have this meeting about 1 week before the next general Working Group meeting:

  • https://github.com/graphql/graphql-wg/blob/master/agendas/2020-04-02.md

Current champions: @leebyron @binaryseed @eapache @benjie

closed time in 2 months

binaryseed

issue commentgraphql/graphql-wg

GraphQL @defer and @stream

Closing this issue since it's now a recurring agenda item!

Keweiqu

comment created time in 2 months

issue closedgraphql/graphql-wg

GraphQL @defer and @stream

We’ve been experimenting with @defer and @stream at Facebook for a while now -- Lee first discussed the idea of @defer and @stream in 2016. Over the last three years, we've done a ton of iterations as we uncovered and resolved issues and edge cases following that initial approach. We're now seeing a renewed demand for these ideas in the open source community: https://github.com/graphql/graphql-js/pull/2318 https://github.com/graphql/graphql-js/pull/2319

Given that Facebook’s increased internal usage makes us more confident in our approach, it seems like a good time to start a discussion of what the next steps would be. Opening this issue with some strategic questions:

  • What's the best way to drive @defer and @stream standardization?
  • Should these features be part of the official spec or a supplemental specification (e.g. connections)?
  • If we decide these features are worthy of standardization, what's the best way of driving towards alignment? Should we set up a stream/defer focused-WG?

closed time in 2 months

Keweiqu

issue commentgraphql/graphql-wg

[2020-05-07] Include defer/stream problem statements in RFC doc

I believe this was handled by https://github.com/graphql/graphql-spec/pull/717 - is there more to do @robrichard ?

leebyron

comment created time in 2 months

issue closedgraphql/graphql-wg

[2020-05-07] Making sure we have agenda items for the rest of the year

https://github.com/graphql/graphql-wg/blame/master/notes/2020-05-07.md#L29

closed time in 2 months

leebyron

issue commentgraphql/graphql-wg

[2020-05-07] Making sure we have agenda items for the rest of the year

Closed by 0675a8037b874205091cad1897634abb8a3793bb

leebyron

comment created time in 2 months

push eventgraphql/graphql-wg

Lee Byron

commit sha ec8b12a126bf200a602e62e8cdcdee201af6507a

Update links to action items

view details

push time in 2 months

issue openedgraphql/graphql-wg

[2020-05-07] Include defer/stream problem statements in RFC doc

https://github.com/graphql/graphql-wg/blame/master/notes/2020-05-07.md#L168

created time in 2 months

issue openedgraphql/graphql-wg

Add InputUnion solution criteria that error messages are well specified

https://github.com/graphql/graphql-wg/blame/master/notes/2020-05-07.md#L120

created time in 2 months

issue openedgraphql/graphql-wg

Update Input Union RFC after recent subcommittee meetings

https://github.com/graphql/graphql-wg/blame/master/notes/2020-05-07.md#L104

created time in 2 months

more