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
The @escape.tech/graphql-armor-block-field-suggestions package does what it promises. However, when masking suggestions, it leaves the leading whitespace and trailing question mark in place. I.E. the original unmasked message Cannot query field "i" on type "Node". Did you mean "id"? becomes Cannot query field "i" on type "Node". [Suggestion hidden]? without overriding the default mask. When mask is overridden with the empty string the result message is Cannot query field "i" on type "Node". ?.
I'd expect outputs of:
Cannot query field "i" on type "Node". [Suggestion hidden] with default settings
Cannot query field "i" on type "Node". with mask overridden with the empty string
The text was updated successfully, but these errors were encountered:
The
@escape.tech/graphql-armor-block-field-suggestions
package does what it promises. However, when masking suggestions, it leaves the leading whitespace and trailing question mark in place. I.E. the original unmasked messageCannot query field "i" on type "Node". Did you mean "id"?
becomesCannot query field "i" on type "Node". [Suggestion hidden]?
without overriding the default mask. When mask is overridden with the empty string the result message isCannot query field "i" on type "Node". ?
.I'd expect outputs of:
Cannot query field "i" on type "Node". [Suggestion hidden]
with default settingsCannot query field "i" on type "Node".
with mask overridden with the empty stringThe text was updated successfully, but these errors were encountered: