Skip to content
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

Testing contexts should allow for implicit access of non-exported interfaces #143

Open
brekk opened this issue Mar 30, 2024 · 0 comments
Open

Comments

@brekk
Copy link
Contributor

brekk commented Mar 30, 2024

There is prevailing wisdom to the contrary, but sometimes there's a good reason to have a white-box test which allows one to test against the internals of the library. Currently export semantics apply to downstream consumers, so anything not exported is implicitly private.

This request is to allow for the possibility of accessing otherwise private / inaccessible members from within a testing context.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant