-
Notifications
You must be signed in to change notification settings - Fork 153
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
Warnings on well formatted GraphQL files #465
Labels
Comments
Hi @p-makowski. Thank you for your report. Join Magento Community Engineering Slack and ask your questions in #github channel. |
@magento I am working on this |
m2-community-project
bot
added
Progress: dev in progress
and removed
Progress: ready for grooming
labels
Sep 13, 2023
p-makowski
added a commit
to p-makowski/magento-coding-standard
that referenced
this issue
Sep 13, 2023
…e type definitions
p-makowski
added a commit
to p-makowski/magento-coding-standard
that referenced
this issue
Sep 13, 2023
…e type definitions - unit tests adjusted
m2-community-project
bot
added
Progress: PR created
and removed
Progress: dev in progress
labels
Sep 19, 2023
p-makowski
added a commit
to p-makowski/magento-coding-standard
that referenced
this issue
Oct 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Preconditions
The bug is reproducible in custom Magento modules that have schema.graphqls files written in readable manner, so e.g. with new line breaks or indentation.
A rule that those not work well with well formatted files is Magento2.GraphQL.ValidTypeName.NotCamelCaps.
Steps to reproduce
vendor/bin/phpcs -s schema.graphqls
Expected result
No warnings discovered.
Actual result
The text was updated successfully, but these errors were encountered: