Remove notice about removing typeConfigDecorator from UPGRADE.md since we reverted this change and it still exists

This commit is contained in:
Vladimir Razuvaev 2018-03-26 12:28:11 +08:00
parent 2913f07050
commit a1b1436f7d

View File

@ -38,13 +38,6 @@ Exception inside `parseLiteral()`, `parseValue()` and `serialize()`.
Returning null from any of these methods will now be treated as valid result. 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 ### 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 Most users won't be affected. It *may* affect you only if you do your own manipulations
with exported AST. with exported AST.