-
Notifications
You must be signed in to change notification settings - Fork 6.8k
move some things from cdk/testing to cdk/private/testing #16621
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
Conversation
this is in preparation for when we publish cdk/testing with the component harness infrastructure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather than calling it internal-testing
, should we make something similar to the @angular/private/testing
from angular/angular?
That sounds good as long as it works. I know some of our scripts don't really expect to deal with tertiary entry points, but it might be ok since we're not publishing it. I'll try putting it under |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM in general. I think we should create a golden file for the testing entry-point? can you create one?
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This is in preparation for when we publish cdk/testing with the component harness infrastructure. cdk/private/testing will be an unpublished package that we use for our own shared testing utilities.
I've also added
@docs-private
to all symbols that remain in cdk/testing. They are not really intended to be used directly (at least not until we review the API and add docs and tests), instead they will be used by the harness infrastructure which will be a public API.