You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no way to differentiate between a simple interface definition and an actual class implementation (see image below).
In a perfect world, there'd be some way to differentiate between the TransportLayer interface definition and the WPGraphQL class. Currently both of these have identical scopes.
Thanks for the consideration!
The text was updated successfully, but these errors were encountered:
If the suggestion above doesn't really work, an alternative that would be nice also in my case would be to be able to differentiate between interface/class/type definitions and implementations.
So, for example...
interfaceFoo{bar: string;}typeT=Foo;// line 5interfaceBar{foo: Foo;// line 7}
Where Foo on line 1 could be scoped differently than when it's used on lines 5 and 7.
The use-case here being to create a syntax theme that allows for quick identification of types being defined and types being consumed.
(I will admit, this is super nit-picky! I do appreciate the consideration though nevertheless)
TS and JS Grammar Extension version: 0.0.18 / latest
There is currently no way to differentiate between a simple interface definition and an actual class implementation (see image below).
In a perfect world, there'd be some way to differentiate between the
TransportLayer
interface definition and theWPGraphQL
class. Currently both of these have identical scopes.Thanks for the consideration!
The text was updated successfully, but these errors were encountered: