graphql-php/src/Utils
Daniel Tschinder 022c490011 RFC: Descriptions as strings
As discussed in facebook/graphql#90

This proposes replacing leading comment blocks as descriptions in the schema definition language with leading strings (typically block strings).

While I think there is some reduced ergonomics of using a string literal instead of a comment to write descriptions (unless perhaps you are accustomed to Python or Clojure), there are some compelling advantages:

* Descriptions are first-class in the AST of the schema definition language.
* Comments can remain "ignored" characters.
* No ambiguity between commented out regions and descriptions.

Specific to this reference implementation, since this is a breaking change and comment descriptions in the experimental SDL have fairly wide usage, I've left the comment description implementation intact and allow it to be enabled via an option. This should help with allowing upgrading with minimal impact on existing codebases and aid in automated transforms.

BREAKING CHANGE: This does not parse descriptions from comments by default anymore and the value of description in Nodes changed from string to StringValueNode
2018-02-10 18:44:51 +01:00
..
AST.php Fixed minor error in docblock comment 2017-08-21 00:19:07 +07:00
BlockString.php RFC: Block String 2018-02-10 18:43:26 +01:00
BuildSchema.php RFC: Descriptions as strings 2018-02-10 18:44:51 +01:00
FindBreakingChanges.php testDetectsAdditionsToUnionType 2017-11-21 12:18:28 -05:00
MixedStore.php Global config; descriptor moved to appropriate namespace; minor cleanup 2017-07-12 13:16:34 +07:00
PairSet.php Consistent coding style + doc block comments for Types and Utils 2016-10-17 19:14:29 +07:00
SchemaPrinter.php RFC: Descriptions as strings 2018-02-10 18:44:51 +01:00
TypeComparators.php Schema validation + tests (#148) 2017-08-13 23:04:03 +07:00
TypeInfo.php Fix how TypeInfo handles inline fragments without type 2018-02-09 14:32:44 +01:00
Utils.php Fix Utils::printSafe with bool true 2018-02-02 08:18:46 +01:00