Skip to content

Conversation

@dobrevad
Copy link
Contributor

@dobrevad dobrevad commented May 4, 2022

Add the capability to extend a harness without having to duplicate the with method
used to load it. This was necessary before because the returned predicate was of type
the parent harness which resulted in loading a harness instance of the parent type
instead of the derived class unless the method is overridden.

Add the capability to extend a harness without having to duplicate the `with` method
used to load it. This was necessary before because the returned predicate was of type
the parent harness which resultet in loading a harness instance of the parent type
instead of the derived class unless the method is overridden.
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent action: merge The PR is ready for merge by the caretaker merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed target: rc This PR is targeted for the next release-candidate labels May 5, 2022
@crisbeto
Copy link
Member

crisbeto commented May 5, 2022

Commit message fixup: should be a fix instead of a test.

@crisbeto crisbeto self-assigned this May 5, 2022
@crisbeto crisbeto merged commit 14694c8 into angular:main May 5, 2022
crisbeto pushed a commit that referenced this pull request May 5, 2022
Add the capability to extend a harness without having to duplicate the `with` method
used to load it. This was necessary before because the returned predicate was of type
the parent harness which resultet in loading a harness instance of the parent type
instead of the derived class unless the method is overridden.

(cherry picked from commit 14694c8)
@dobrevad dobrevad deleted the harness branch May 5, 2022 17:30
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker merge: fix commit message When the PR is merged, rewrites/fixups of the commit messages are needed P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants