Directives are ignored when using maps as changesets
- 主要言語
- Go
- スター
- 10.8k
- フォーク
- 1.3k
- 平均マージ
- 2日 36分
- マージ済み PR(30日)
- 26
説明
### What happened?
I have defined some directives on several fields on several input types as described here: https://gqlgen.com/reference/directives/ .
In my application I needed the functionality described here: https://gqlgen.com/reference/changesets/ . So I did override the model for some input types with `map[string]interface{}`.
In the generated code the calls that are related to the directives appear inside the `func (ec *executionContext) unmarshalInputMyInputType(ctx context.Context, obj interface{}) (model.MyInputType, error) {` function, which is never called and there is no way to trigger it manually.
### What did you expect?
I would expect the code that is related to the directives to be independent from the unmarshal function and to still be triggeredor at least be able to call it manually inside my resolvers.
### Minimal graphql.schema and models to reproduce
``` graphql
input MyInputType {
foo: Float @rangeInt(min: 0, max: 10)
}
```
gqlgen.yml
```
models:
MyInputType:
model: "map[string]interface{}"
```
### versions
- `gqlgen version`: v0.14.0
- `go version`: 1.17.2
コントリビューションガイド
評価
この issue はまだ評価されていません。