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

several fixes #1198

Merged
merged 1 commit into from
Oct 8, 2022
Merged

several fixes #1198

merged 1 commit into from
Oct 8, 2022

Conversation

dimaMachina
Copy link
Owner

  • fix passing pluck config via graphql-config#extensions field
  • rename extensions.graphqlTagPluck to extensions.pluckConfig
  • fix performance regression while using processor: '@graphql-eslint/graphql'

@changeset-bot
Copy link

changeset-bot bot commented Oct 8, 2022

🦋 Changeset detected

Latest commit: d2a1fae

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@graphql-eslint/eslint-plugin Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@theguild-bot
Copy link
Collaborator

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package Version Info
@graphql-eslint/eslint-plugin 3.11.3-alpha-20221008220048-6ed3933 npm ↗︎ unpkg ↗︎

rename `extensions.graphqlTagPluck` to `extensions.pluckConfig`
fix performance regression while using `processor: '@graphql-eslint/graphql'`
@dimaMachina dimaMachina merged commit 2886adf into master Oct 8, 2022
@dimaMachina dimaMachina deleted the fix-pluck-options branch October 8, 2022 23:00
dimaMachina added a commit that referenced this pull request Dec 20, 2022
rename `extensions.graphqlTagPluck` to `extensions.pluckConfig`
fix performance regression while using `processor: '@graphql-eslint/graphql'`
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