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
IMO if an interface/type is used by something that's exported, it'd be good to export SomeSettings. That way if future folks want to use it, they won't have issues trying to import it.
Waiting until that issue is either accepted or declined
If it's accepted, merging the PR into typescript-eslint
If it's declined, either making the rule in an existing community plugin (I don't know which if any would be a good place) or making a new plugin with the rule
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Bug Report Checklist
main
branch of the repository.Overview
I see code like this a lot:
IMO if an interface/type is used by something that's exported, it'd be good to export
SomeSettings
. That way if future folks want to use it, they won't have issues trying to import it.Additional Info
Similar issue here: webpro-nl/knip#127.
I think part of this work should be:
Seeing if it already exists in https://github.com/typescript-eslint/typescript-eslint/issuesIf it doesn't yet exist, filing a proper issue thereI filed it: Rule proposal: Export all types used in exports typescript-eslint/typescript-eslint#7670The text was updated successfully, but these errors were encountered: