feat: graphql-tag-pluck options
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #1155
Type of change
Please delete options that are not relevant.
- [x] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [x] This change requires a documentation update
Screenshots/Sandbox (if appropriate/relevant):
Adding links to sandbox or providing screenshots can help us understand more about this PR and take action on it as appropriate
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
- [x] processor-without-config.spec: tests the processor as usual without any
graphql-configusing custom tags - [x] processor-with-config.spec: tests the processor with
graphql-configconfigured to use custom tags
Test Environment:
- OS: macOS Monterey
-
@graphql-eslint/[email protected] - NodeJS: v16.14.1
Checklist:
- [x] I have followed the CONTRIBUTING doc and the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [x] I have added tests that prove my fix is effective or that my feature works
- [x] New and existing unit tests and linter rules pass locally with my changes
- [x] Any dependent changes have been merged and published in downstream modules
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
🦋 Changeset detected
Latest commit: bd27e4c4b1064cb6b9bd23f1acf1a8c3c33e3b3b
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 | Minor |
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
It looks like the test / Lint / eslint (pull_request) action failed due to insufficient resources so it just needs to be rerun
It looks like the
test / Lint / eslint (pull_request)action failed due to insufficient resources so it just needs to be rerun
@B2o5T this issue happens because of the shared-config task, ~~I'll fix it now~~ I think it's fixed now.
@JimmyPaolini I'll try to re-run
ok seems to be fine now :) @B2o5T @TuvalSimha can you please take a look?
Will take care of this in current sprint!
released in @graphql-eslint/[email protected]
@B2o5T Thanks so much for this!! 😄