diff options
| author | Eugen Wissner <belka@caraus.de> | 2020-09-14 07:49:33 +0200 |
|---|---|---|
| committer | Eugen Wissner <belka@caraus.de> | 2020-09-15 08:06:07 +0200 |
| commit | 4c10ce92041dc73a95aeb64aca241dd937ffaa5c (patch) | |
| tree | 6a1742eaf6ff3ae3a4f4d0e2a3c5afbe9a146f4b /CHANGELOG.md | |
| parent | 08998dbd935e65aab10ff53c249cb214af2522f2 (diff) | |
| download | graphql-4c10ce92041dc73a95aeb64aca241dd937ffaa5c.tar.gz | |
Use Seq as base monad in the validator
It is more natural to implement the logic: try to apply each rule to
each node.
Diffstat (limited to 'CHANGELOG.md')
| -rw-r--r-- | CHANGELOG.md | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index 378814d..85ffcf1 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,9 +10,16 @@ and this project adheres to ### Changed - `AST.Document.Selection` wraps additional new types: `Field`, `FragmentSpread` and `InlineFragment`. Thus validation rules can be defined more concise. +- `AST.Document.Argument` contains the argument location. +- `AST.Lexer.colon` ignores the result (it is always a colon). +- `Validate.Validation`: `Validation.rules` was removed. `Validation.rules` + contained the list of rules, but the executed rules shouldn't know about other + rules. `rules` was a part of the `Validation` context to pass it easier + around, but since the rules are traversed once now and applied to all nodes in + the tree at the beginning, it isn't required anymore. ### Added -- `Validate.Validation.Rule`: `SelectionRule`, `FieldRule`, `FragmentRule` and +- `Validate.Validation.Rule`: `SelectionRule`, `FieldRule`, `FragmentRule`, `FragmentSpreadRule` constructors. - `Validate.Rules`: - `fragmentsOnCompositeTypesRule` |