Skip to content

Fix naming conventions and optional/required fields in company GraphQL schema #447

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

Merged
merged 2 commits into from
Oct 22, 2020

Conversation

melnikovi
Copy link
Member

@melnikovi melnikovi commented Oct 2, 2020

Problem

Fix naming conventions and optional/required fields.

Solution

Requested Reviewers

children: [CompanyAclResource!] @doc(description: "An array of sub-resources.")
}

type CompanyRoleNameCheckResponse @doc(description: "Response object schema for a role name validation query.") {
isNameValid: Boolean @doc(description: "Role name validation result")
is_name_valid: Boolean @doc(description: "Role name validation result")

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not super important. Boolean can be made mandatory. (Boolean!)

@melnikovi melnikovi merged commit 405c91f into magento:master Oct 22, 2020
@melnikovi melnikovi changed the title Fix naming conventions and optional/required fields Fix naming conventions and optional/required fields in company GraphQL schema Oct 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants