-
-
Notifications
You must be signed in to change notification settings - Fork 30.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose _NamespacePath
#119668
Comments
Signed-off-by: Filipe Laíns <[email protected]>
I'll have to look around to see if I can dig up the previous discussion, but +1! |
I don't think we thought it should be hidden, rather there was just no reason to expose it. What's the need for accessing it? If it's at all compelling, then I'm +1. |
For my specific case, I am loading data from a namespace package, or rather, I need to point to the directories containing said data. This could also be solved by |
Feature or enhancement
Proposal:
Currently,
_NamespacePath
is prefixed as a private type, but since it's exposed, it should be marked as public API. I have a specific case in mind where I want to do an instance check.I vaguely remember a discussion somewhere with @warsaw where this was mentioned, but I can't find it.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
Links to previous discussion of this feature:
No response
Linked PRs
The text was updated successfully, but these errors were encountered: