Replies: 1 comment 1 reply
-
I agree that it might be better to rename it, although not because of GraphQL. GraphQL or Typescript using that "type" keyword will not create any difficulties whatsoever.
Having said that, I'm not the biggest fan of "type" either. My reasoning is not just reserved keywords but
The v2-interfaces already implement a workaround for From your proposal, |
Beta Was this translation helpful? Give feedback.
-
This is how we are currently defining the
ContractType
,StreamType
, and theActionType
:My concern is that this key can be easily mingled with the reserved
type
keyword in GraphQL - I am surprised that GraphQL even allows this word to be used as a key within an actual type.Proposed alternatives to clear up any doubt:
class
category
entityType
Beta Was this translation helpful? Give feedback.
All reactions