Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OverlappingFieldsCanBeMergedRule suggestions #15

Conversation

yaacovCR
Copy link
Collaborator

@yaacovCR yaacovCR commented Sep 3, 2024

-- Removes visiting fragment definitions in favor of a replaceFragmentVariables() utility function that essentially only visits the variables within fragments.
-- Renames "fragment names" throughout the file to refer to "fragment spreads."

Copy link

github-actions bot commented Sep 3, 2024

Hi @yaacovCR, I'm @github-actions bot happy to help you with this PR 👋

Supported commands

Please post this commands in separate comments and only one per comment:

  • @github-actions run-benchmark - Run benchmark comparing base and merge commits for this PR
  • @github-actions publish-pr-on-npm - Build package from this PR and publish it on NPM

@yaacovCR yaacovCR force-pushed the validation-suggestions branch from aabf95d to 2343bc0 Compare September 3, 2024 08:27
@JoviDeCroock JoviDeCroock merged commit 21a9185 into JoviDeCroock:fragment-args-typeinfo-2024 Sep 3, 2024
14 of 15 checks passed
@yaacovCR yaacovCR deleted the validation-suggestions branch September 3, 2024 08:30
JoviDeCroock added a commit that referenced this pull request Sep 4, 2024
* Add typeinfo functionality as a run-up to supporting the new validation
rules

Co-authored-by: mjmahone <[email protected]>

* Fragment arguments validation (#5)

* Fragment args validation

* add experimental substitution

* validation suggestions (#12)

* validation suggestions

* remove OperationSignature from ValidationContext

only used in one rule, does not need to be on context

remove dependency on getVariableSignature

move FRAGMENT_ARGUMENT below ARGUMENT

fragment arguments do not have location defaults

only variable defaults => so getDefaultValue(), which returns location defaults for use with the allowedVariableUsage helper, should never be called by getVariableUsages with respect to fragment arguments

fragment arguments therefore need not add anything to the default value stack

reduce diff from main

these diffs crept in before Kind.FRAGMENT_ARGUMENT was separated out

---------

Co-authored-by: Yaacov Rydzinski <[email protected]>

* OverlappingFieldsCanBeMergedRule suggestions (#15)

---------

Co-authored-by: mjmahone <[email protected]>
Co-authored-by: Yaacov Rydzinski <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants