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
{{ message }}
This repository has been archived by the owner on Jun 1, 2023. It is now read-only.
It looks like you could avoid the redundant namespace by using the @warn_unqualified_access annotation. Unfortunately, this only applies to function declarations, but I think we should extend that to top-level variables and constants, too
That feels like a hack, and I assume the types would still be imported into the global namespace, just not usable without a warning.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In my project, I use a an
enum
as namespacing and nest all my types inside it.The main page looks like this: https://sindresorhus.com/playground/ However, I would like to make https://sindresorhus.com/playground/KeyboardShortcuts/ the main page. Maybe some config where I could specify the
KeyboardShortcuts
enum as the entry type.The text was updated successfully, but these errors were encountered: