Skip to content

fix: make wrapper component standalone: false explicitly #498

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 9, 2024
Merged

fix: make wrapper component standalone: false explicitly #498

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions projects/testing-library/src/lib/models.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -473,6 +473,7 @@ export interface RenderTemplateOptions<WrapperType, Properties extends object =
* @description
* An Angular component to wrap the component in.
* The template will be overridden with the `template` option.
* NOTE: A standalone component cannot be used as a wrapper.
*
* @default
* `WrapperComponent`, an empty component that strips the `ng-version` attribute
Expand Down
2 changes: 1 addition & 1 deletion projects/testing-library/src/lib/testing-library.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -616,7 +616,7 @@ if (typeof process === 'undefined' || !process.env?.ATL_SKIP_AUTO_CLEANUP) {
}
}

@Component({ selector: 'atl-wrapper-component', template: '' })
@Component({ selector: 'atl-wrapper-component', template: '', standalone: false })
class WrapperComponent {}

/**
Expand Down