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's no reason we shouldn't support the gradual migration of projects. We can run both tools and fill a common SuffixTree. The config directives will have to be redesigned, as they currently assume JS xor TS.
The text was updated successfully, but these errors were encountered:
This adds a role for interface cross referencing. It also updates
`ts_type_xref_formatter` to take a third argument "kind" which indicates which
type of object we're referring to so that we can generate proper xrefs. TODO: We
should probably move this field onto the XRefInternal object.
There's no reason we shouldn't support the gradual migration of projects. We can run both tools and fill a common SuffixTree. The config directives will have to be redesigned, as they currently assume JS xor TS.
The text was updated successfully, but these errors were encountered: