Skip to content

extendSchema: Use consistent naming + inline 'getExtendedType' func#1327

Merged
mjmahone merged 1 commit intographql:masterfrom
IvanGoncharov:extendRename
May 14, 2018
Merged

extendSchema: Use consistent naming + inline 'getExtendedType' func#1327
mjmahone merged 1 commit intographql:masterfrom
IvanGoncharov:extendRename

Conversation

@IvanGoncharov
Copy link
Copy Markdown
Member

Based on this discussion: #1322 (comment)
I think naming should be consistent with types and predicates:

export function isType(type: mixed): boolean %checks {
return (
isScalarType(type) ||
isObjectType(type) ||
isInterfaceType(type) ||
isUnionType(type) ||
isEnumType(type) ||
isInputObjectType(type) ||
isListType(type) ||
isNonNullType(type)
);
}

export function isNamedType(type: mixed): boolean %checks {
return (
isScalarType(type) ||
isObjectType(type) ||
isInterfaceType(type) ||
isUnionType(type) ||
isEnumType(type) ||
isInputObjectType(type)
);
}

@leebyron
Copy link
Copy Markdown
Contributor

Makes sense to me - do you mind rebasing?

@IvanGoncharov
Copy link
Copy Markdown
Member Author

@leebyron Rebased

@mjmahone mjmahone merged commit 0276d68 into graphql:master May 14, 2018
@mjmahone
Copy link
Copy Markdown
Contributor

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants