Skip to content

@testable cleanup #8826

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

Draft
wants to merge 46 commits into
base: main
Choose a base branch
from
Draft

@testable cleanup #8826

wants to merge 46 commits into from

Conversation

compnerd
Copy link
Member

This series cleans up the vast majority of the @testable importing in the tests. The one that remains is for X509 which is external to this package. I intend to introduce a SPI for that API surface to help remove the last of the @testable importing.

compnerd added 30 commits June 13, 2025 13:56
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
These do not require additonal APIs to be exposed, simply convert to
regular import of the Basics module.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
compnerd added 16 commits June 13, 2025 18:36
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
This extends the visibility of some of the private implementation to the
package level to allow use for testing without `@testable` imports.
Use the newly extended APIs for testing and use a non-testable import of
the package, avoiding a recompilation.
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

Successfully merging this pull request may close these issues.

1 participant