chore: replace byComponent
"by" By.directive
& rm getComponentSelector
#896
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It does the same! However, our util was flakier, as it looked by the component selector. There have been some talking around to remove selectors. So using the DI system as
By.directive
does to look for the item is a stronger approach.Then,
getComponentSelector
is only used by the test helper ensuring content projection is performed for the component. However, can get rid of that by specifying a custom selector for the component under test usingTestBed.overrideComponent
. So doing that and removing that function.Finally,
isClass
can be removed as there are no usages of it