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.
As of #146, we have a growing number of
@exportstatements 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.