[TypeScript Resolvers] The default name for interfaces should not contains "I" prefix
See original GitHub issueI suppose naming generation should be consistent. These tree interfaces are prefixed with I
.
ISubscriptionResolverObject
IResolvers
IDirectiveResolvers
I think they should be:
SubscriptionResolverObject
Resolvers
DirectiveResolvers
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Doesn't avoiding the initial I for interfaces in TypeScript lead to ...
The first thing you're worried about, when you're deciding to refuse I prefix, is: "I don't want to name my classes like class...
Read more >IInterface Considered Harmful - Okta Developer
This post discusses the disadvantages of using the 'I' prefix for interfaces in static-typed languages.
Read more >typescript-resolvers - GraphQL Code Generator
This plugin generates TypeScript signature for resolve functions of your GraphQL API. You can use this plugin to generate simple resolvers ...
Read more >Do not prefix TypeScript interface names - Today I Learned
So there is no need anymore for naming conventions like IMyInterface or AMyAbstractClass .
Read more >Documentation - Module Resolution - TypeScript
Finally, if the compiler could not resolve the module, it will log an error. ... The net result is that modules at runtime...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@dotansimha Yes I used the
init
command and it installed version 1.0 of the pluginsI see, thanks @lednhatkhanh , we’ll take a look 😃