You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes the bug #1680 that necessitated adding the 'name' parameter to the @model directive, regardless of the name of the GraphQL object type's name. (#1706)
## Why make this change?
- Closes#1680
- Regression introduced in 0.8.49 caused required explicitly adding
"name" directive for all the model/entity irrespective of whether we are
using a different name than the one it originally has.
- Regression introduced in #1402 when we started using
TryExtractGraphQLName as follows:
```
string typeName = GraphQLUtils.TryExtractGraphQLFieldModelName(underlyingType.Directives, out string? modelName) ?
modelName :
underlyingType.Name;
```
## What is this change?
Checking Directive "name" exists before accessing its value.
## How was this tested?
Tested locally for now. Will be checking Test cases for it.
- [x] Integration Tests
- [ ] Unit Tests
---------
Co-authored-by: Neeraj Sharma <[email protected]>
0 commit comments