From a1b1436f7d5264a2b8289d33aaaa4154b24a9b28 Mon Sep 17 00:00:00 2001 From: Vladimir Razuvaev Date: Mon, 26 Mar 2018 12:28:11 +0800 Subject: [PATCH] Remove notice about removing typeConfigDecorator from UPGRADE.md since we reverted this change and it still exists --- UPGRADE.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/UPGRADE.md b/UPGRADE.md index 8126010..d95cef5 100644 --- a/UPGRADE.md +++ b/UPGRADE.md @@ -38,13 +38,6 @@ Exception inside `parseLiteral()`, `parseValue()` and `serialize()`. Returning null from any of these methods will now be treated as valid result. -### Breaking: TypeConfigDecorator was removed from BuildSchema -TypeConfigDecorator was used as second argument in `BuildSchema::build()` and `BuildSchema::buildAST()` to -enable generated schemas with Unions or Interfaces to be used for resolving. This was fixed in a more -generalised approach so that the TypeConfigDecorator is not needed anymore and can be removed. - -The concrete Types are now resolved based on the `__typename` field. - ### Possibly Breaking: AST to array serialization excludes nulls Most users won't be affected. It *may* affect you only if you do your own manipulations with exported AST.