Skip to content

Clean up exported testing and API surfaces #147

Open
@dibenede

Description

@dibenede

As of #146, we have a growing number of @export statements that have been added for the sake of closure optimizations while preserving tests. However, a lot of the exported surfaces are deeply internal to the project.

We should try to simplify our exports and perhaps rethink our testing strategy to separate invasive unit tests from more integration-like tests that only need public surfaces.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions