GraphQL: TMP add data (old changes)

Author: vwkd

content/languages/graphql/idl/index.md

@@ -225,6 +225,8 @@ InputValueDefinition:
     Description* Name : Type DefaultValue* Directives*
 ```
 
+at least one field
+
 - `NamedType` in `ImplementsInterfaces` must be name of an interface, see Abstract types
 - `Type` in `InputValueDefinition` must be an input type, see Input Type
 
@@ -233,6 +235,9 @@ InputValueDefinition:
 
 - interface: abstract object type
 
+??? ~~restricts type hierarchies to a single level~~ can be multiple
+~~no inheritance~~ limited inheritance
+
 ```plaintext
 InterfaceTypeDefinition:
     Description* "interface" Name ImplementsInterfaces* Directives* FieldsDefinition*
@@ -392,6 +397,10 @@ InputFieldsDefinition:
 
 ## Directive
 
+a way to extend the language
+allow tools to add custom behavior
+to just about any aspect of the type system
+
 ```plaintext
 DirectiveDefinition
     Description* "directive" @ Name ArgumentsDefinition* "on" DirectiveLocations
@@ -413,9 +422,16 @@ TypeSystemDirectiveLocation:
 
 - name of directive must be unique, not start with two underscores since reserved for introspection
 - directive can't use other directive in argument that creates a cyclic reference, e.g. itself
+???
+can mark as `repeatable` to use multiple times
+order matters
 - built-in directives in any schema engine:
     - `@deprecated(reason: String)` on field or enum: marks field or enum value as deprecated in schema
-- beware: currently spec doesn't include `@deprecated` on argument, see [#525](https://github.com/graphql/graphql-spec/pull/525)
+@specifiedBy(url:) url of format of custom scalar
+??? Allows to use same name for multiple different types
+
+
+??? beware: currently spec doesn't include `@deprecated` on argument, see [#525](https://github.com/graphql/graphql-spec/pull/525)
 
 
 

content/languages/graphql/index.md

@@ -9,4 +9,76 @@ tags:
 
 - API query language and IDL
 - API query language is designed for JSON responses
-- IDL makes documentation first-class, e.g. via introspection
+- IDL makes documentation first-class, e.g. via introspection
+
+//// nordicapis
+
+predetermined, knowable format
+
+application layer query language
+
+interprets strings from the client, and returns data in an understandable, predictable, pre-defined manner
+-> client specifiers what wants, gets what specifies
+
+client defines the expected data format
+
+single endpoint
+variable request call
+eliminates ad hoc endpoints and roundtrip object retrievals
+
+layer between data and client, can transform, aggregate, bridge the gap, without either side having to sacrifice flexibility
+
+single request, no n+1 problem
+automatically joins
+
+allows to select subset
+allows to alias names
+
+server publishes clear and explicit rules, types
+can validate query ahead of time against schema
+
+introspect schema, understand API better, self-documenting
+
+/// spec
+
+a query language and execution engine
+
+
+///// ?
+
+can save static query on server, just send identifier and variables from client
+
+//// Lee Byron talk
+
+- fast
+bundle multiple request and response in one
+describes what needs upfront
+single round trip
+can only get subset of what needs
+- robust
+response shape guarantees
+no crashes because unexpected format
+static types, schema
+- self-documenting
+no manual out-of-date documentation
+static analysis locally
+- faster development
+additional layer, decouples client further from server, aliasing, etc.
+
+no need to version
+
+//// benjie talk
+
+tooling, linting, code generation works with any GraphQL API thanks to schema
+
+//// meta guys talk
+
+layer makes looser coupling, constant endpoint, etc.
+
+separate problems of server from problems of client
+
+/// yelp guy
+
+if field is unexpectedly null, then sets parent to null, walks up the tree until fiends nullable field, never sends null where expected non-null
+
+null in non-null field bubbles up to next nullable field

content/languages/graphql/introduction/index.md

@@ -23,6 +23,8 @@ ExecutableDefinition:
 
 - beware: differs from spec, spec allows for partial documents and mixes of query language and IDL, here assume document contains either executable operations or single schema, see [#788](https://github.com/graphql/graphql-spec/issues/788#issuecomment-721298885) ⚠️
 
+spec has multiple documents, i.e. grammar has multiple root nodes, doesn't make sense, should just have one root node and say can implement only some of the options, currently this is implcit outside the spec in the word "GraphQL" which might refer to any one of those 4 without further clarification
+
 
 
 ### Grammar

content/languages/graphql/query-language/index.md

@@ -456,6 +456,33 @@ query getUser ($showAge: Boolean) {
 - fragment can't use other fragment that creates a cyclic reference, e.g. itself
 
 
+@defer and @stream
+
+for lowering time to response of expensive operations
+client says what isn't as important, what can be sent later, what can be deprioritized
+additional patches get sent over same connection
+?? errors stop the stream
+
+over HTTP multipart response with chunked encoding
+see GraphQL over HTTP spec ?!?!
+
+response object gets `hasNext` property, subsequent responses also a `path` where to apply the patch in previously received data
+
+only on fragment spread or inline fragment
+can use fragment spread with single field
+
+not allowed on root mutation field because would change the order
+
+act as null boundaries, can't bubble up null since already sent previous patches
+sets whole data to null !?!
+also the error then stops the streaming !?!
+
+
+## Subscription
+
+for long running events
+
+
 
 ## Resources