profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/joshprice/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

graphql-elixir/graphql 858

GraphQL Elixir

graphql-elixir/plug_graphql 125

Plug (Phoenix) integration for GraphQL Elixir

graphql-elixir/hello_graphql_phoenix 97

Examples of GraphQL Elixir Plug endpoints mounted in Phoenix

gausby/gen_mqtt 62

DEPRECATED (use Tortoise instead): An Elixir behaviour that makes it possible to communicate with a MQTT server

filterfish/rantomania 2

rantomania

joshprice/bucketwise 2

A web-based personal finance manager with a focus on non-OCD budgeting and avoiding credit card debt

joshprice/cardwall-prototype 2

Build your own cardwall

joshprice/coconut 2

A jQuery plugin designed to simplify and guide the OO encapsulation of client side Javascript code and more...

beamuav/groundstation 1

Groundstation

graphqlsydney/graphqlsydney 1

The GraphQL Sydney Meetup

startedhomebound-team/graphql-typescript-factories

started time in 2 hours

created repositorymarkolson/lv-issue-1387

The smallest reproducible code I could find for 1387.

created time in 4 hours

release facebook/flow

v0.154.0

released time in 4 hours

pull request commentgraphql/graphql-js

Backport instanceOf Error Check Improvements

Yay, thanks @tubbo and @IvanGoncharov!

tubbo

comment created time in 5 hours

release ReactiveCocoa/ReactiveSwift

6.6.1

released time in 5 hours

fork syrusakbary/sixtyfps

SixtyFPS is a toolkit to efficiently develop fluid graphical user interfaces for any display: embedded devices and desktop applications. We support multiple programming languages, such as Rust, C++ or JavaScript.

https://sixtyfps.io

fork in 6 hours

startedsixtyfpsui/sixtyfps

started time in 6 hours

startedegoist/yaup

started time in 7 hours

pull request commentabsinthe-graphql/absinthe

Add extend to macro defined schemas

Any news about the issue?

binaryseed

comment created time in 8 hours

issue commentgraphql/graphql-js

Allow schemaPrinter to be customized / extended.

How about we add a config option:

printDirectives: (definition: GraphQLType|GraphQLField|GrapQLEnumValue|GraphQLInputField|GraphQLArgument) => string

Whenever a definition that can hold directives is encountered, the given function would be called with it and is free to print any directives.

j

comment created time in 12 hours

startedreedom/dotenvrc

started time in 14 hours

startedfolke/esbuild-runner

started time in 16 hours

startedmysteriumnetwork/devbook

started time in 19 hours

release influxdata/helm-charts

telegraf-1.8.2

released time in a day

startedastashov/aws-cdk-lambda-typescript-starter

started time in a day

startedzzanehip/The-OldOS-Project

started time in a day

release vercel/swr

1.0.0-beta.7

released time in a day

push eventgraphql/graphql-js

Yaacov Rydzinski

commit sha d1c605668de420b06a5ad4c52af0f98e869198b9

refactor: store ExecutionContext in Executor

view details

Yaacov Rydzinski

commit sha a7743f944ac880898d422ff68941522ee164475c

refactor: spread ExecutionContext properties ...into Executor

view details

Yaacov Rydzinski

commit sha 51c12f1d1d05a6ef15261bc946150612eba44653

refactor: move Executor into separate file

view details

Yaacov Rydzinski

commit sha 72850bd23a8ecddfa184fc8d135ada1562f912bb

introduce ExecutorArgs interface

view details

Yaacov Rydzinski

commit sha 176ea2625f64a09b85ca338b9a2e84ee370146dc

export supporting Executor interfaces ExecutorArgs and ExecutionContext

view details

push time in a day

push eventgraphql/graphql-js

Yaacov Rydzinski

commit sha 049f618d784979278e1acde9abf1d5469b4cf729

introduce ExecutorArgs interface

view details

Yaacov Rydzinski

commit sha 173a7905ffee799bc9b0c3e17434f4955b43e69a

export supporting Executor interfaces ExecutorArgs and ExecutionContext

view details

push time in a day

push eventgraphql/graphql-js

Yaacov Rydzinski

commit sha 38ada75d0b99b1f118ff44c05e50ce84375c834c

refactor: store ExecutionContext in Executor

view details

Yaacov Rydzinski

commit sha 639790e6d547b2a73c38cee13967c78575351ab9

refactor: spread ExecutionContext properties ...into Executor

view details

Yaacov Rydzinski

commit sha 8cf92b7bdb9f927f265d059e3c33ce6cb5b4988c

refactor: move Executor into separate file

view details

push time in a day

pull request commentgraphql/graphql-spec

Spec edits for @defer/@stream

What are the rules regarding duplicate defer fields with the same label. E.g.:

{
  ...GroupAdminFragment @defer(label: "groupAdminDefer")
  ...GroupAdminFragment @defer(label: "groupAdminDefer")
}

fragment GroupAdminFragment {
   managed_groups {
      id
   }
}

In https://github.com/graphql/graphql-spec/pull/742/files#diff-30a69c5a5eded8e1aea52e53dad1181e6ec8f549ca2c50570b035153e2de1c43R1964 it states that the label must be unique. This would mean the query above would be invalid, correct? Is there an additional validation needed to ensure that?

Also: can the label value be a variable? What are the use cased for labels be variables?

robrichard

comment created time in a day

pull request commentgraphql/graphql-js

refactor: execution functions into Executor class

A final (?) thought -- the createSourceEventStream function used to be exported separately, which is no longer necessary, as it is included within the Executor class. This export would not seem to have to be covered by the warning attached to the class, but I am not quite sure how to indicate that and/or how to manage that within the code base. I think the code as is may be just as fine?

Suggestions, thoughts, ideas, conversation....all welcome.

yaacovCR

comment created time in a day

pull request commentgraphql/graphql-js

refactor: execution functions into Executor class

Of important note -- the Executor class is exported, which was the whole reason for this refactoring (!!!). The class is marked as internal, with a comment/warning similar to the Parser class as suggested by @IvanGoncharov (see https://github.com/graphql/graphql-js/pull/3163#issuecomment-859546546).

yaacovCR

comment created time in a day

release vercel/next.js

v11.0.1

released time in a day

pull request commentgraphql/graphql-js

refactor: execution functions into Executor class

#3185 has now been split into the following PR stack: #3192, #3195, #3196, and this PR: #3193

<hr>

Summary:

#3192 introduces the GraphQLAggregateError that forms an independent feature for reporting multiple errors from a resolver, but also allows the buildExecutionContext method to always return a valid ExecutionContext, throwing when impossible, which allows the method to be used in the eventual Executor class constructor. The handleRawError method is introduced, which recognizes that errors may be aggregated.

#3195 moves the subscription code into the execution module -- at long last! -- bringing the reference implementation in line with the spec. Subscriptions within the spec are put on equal footing as queries and mutations, all three being operations that are targets for "execution," with the different execution algorithms further elaborated on within the "Execution" section of the spec. Code reuse is employed to good effect; for example, error handling for subscriptions is streamlined using the same handleRawError method.

#3196 streamlines the buildExecutionContext function and related execution setup code to prepare for integration into the eventual Executor class constructor.

#3193 moves all of the "execution algorithm" functions to the Executor class. execute and subscribe are left as thin wrappers around the Executor class that construct an executor object and call executor.executeQueryOrMutation or executor.executeSubscription, respectively.

<hr>

The subscribe function has been retained because of its different method signature/return type. We could consider introducing query and mutate functions to eventually replace execute so as to properly keep the operations on equal footing.

Thoughts?

yaacovCR

comment created time in a day

push eventgraphql/graphql-js

Yaacov Rydzinski

commit sha f1294d7c22a7dce9c346da0599055854fdcdf80e

refactor: move Executor into separate file

view details

push time in a day

push eventgraphql/graphql-js

Yaacov Rydzinski

commit sha 92f82171190ba801b479bb99fe7d4cacedeeabc4

refactor: spread ExecutionContext properties ...into Executor

view details

push time in a day

push eventgraphql/graphql-js

Yaacov Rydzinski

commit sha 5fbc71408509df46e04fecce32533574d819f983

refactor: executor methods into Executor class This class is exported only to assist people in implementing their own executors without duplicating too much code and should be used only as last resort for cases such as experimental syntax or if certain features could not be contributed upstream. It is still part of the internal API and is versioned, so any changes to it are never considered breaking changes. If you still need to support multiple versions of the library, please use the `versionInfo` variable for version detection.

view details

Yaacov Rydzinski

commit sha 58ba402798cb8182fa5d18d9c7175bf66815de7f

refactor: store ExecutionContext in Executor

view details

push time in a day

release vercel/next.js

v11.0.1-canary.8

released time in a day