chore(deps): update module github.com/99designs/gqlgen to v0.17.43 #91
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.17.41
->v0.17.43
Release Notes
99designs/gqlgen (github.com/99designs/gqlgen)
v0.17.43
Compare Source
What's Changed
New Contributors
Full Changelog: 99designs/gqlgen@v0.17.42...v0.17.43
v0.17.42
Compare Source
7bf0c22
release v0.17.42c811d47e fix: avoid panic from tracing on bad request (#2871)
This fixes a panic which arises from the tracing components when a request has some defect which results in an error when creating the operation context. The transports consistently handle this by calling
DispatchError(graphql.WithOperationContext(ctx, rc), err)
whererc
is the OperationContext which was not correctly constructed. This seems dangerous, because middleware may assume that if there in anOperationContext
in thecontext.Context
than they are being invoked on a normal codepath and can assume their other interceptors have been invoked in the normal order. Also, using a value returned by a function which also returned a non-nil error is very unusual. However, I have no idea what the impact of changing that dangerous behavior in the transports would be, so I opted to make the tracing component more resilient instead.13bb415
fix for entity interfce code gen with related test (#2868)0354649
Remove archived dependency appdash (#2866)0d43599
Update examples go.mod with appdash replacements (#2863)7dd971c
Use defer wg.Done() in FieldSet Dispatch (#2861)24ea195c vikstrous/dataloadgen replaces recommended dataloader package in example docs (#2770)
update example for dataloadgen
improved example with link to example repo
undo unnecessary changes
fix wrong signature
fix creation of loader
Update docs/content/reference/dataloaders.md
42f6e39d Allow fields that return root level definitions (#2858)
generate structs for root level definitions to support fields that return Query, Mutation or Subscription
removed unnecessary comment
re-ran go generate
682a58d
Add go generate for examples so contributors never forget (#2859)e080a96d Modify to prevent unreachable code from occurring (#2846)
fix: 型の数でソートする処理を追加
戻し
fix: case文の最初にスーパークラスが来ないようにする
testdata追加
fix: Added sorting by number of types.
fix: Prevent superclass from appearing at the beginning of case statement
68744ad
Bump changeloge4cf21d
v0.17.41 postrelease bumpConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.