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

fields-are-camel-cased/input-object-values-are-camel-cased are not working #319

Open
isha-talegaonkar opened this issue Jun 27, 2022 · 0 comments

Comments

@isha-talegaonkar
Copy link

isha-talegaonkar commented Jun 27, 2022

Hi,

The above two rules are not working for my schema.

`

   type Friend{
        id: String,
        firstname: String, 
        lastName: String, 
        gender: Gender, 
        age: Int, 
        email: String, 
        contacts: [Contact]
    }
type Contact{
    firstname: String, 
    lastname: String
}

enum Gender{
    MALE
    FEMALE
    OTHER
}

type Query{
    getFriend(id: ID): Friend
}

input FriendInput{
    id: ID,
    firstname: String, 
    lastname: String, 
    gender: Gender, 
    age: Int,
    email: String, 
    contacts: [ContactInput]
}

input ContactInput{
    firstName: String, 
    lastName: String        
}

type Mutation{
    createFriend(input:FriendInput): Friend
}`

When I run the following command, I get this output:

linter_test % graphql-schema-linter --rules fields-are-camel-cased             



✔ 0 errors detected

For the above schema, I expected firstname and lastname to be throwing a camel case error, but they aren't. Do I need to make any changes to the fields-are-camel-cased file before running the command?

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

No branches or pull requests

1 participant