Skip to content

fix(input/testing): filtering by regex not working #20148

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

Merged
merged 1 commit into from
Aug 19, 2020

Conversation

crisbeto
Copy link
Member

The types of the value and placeholder filters allow both a string and a regex, but passing in a regex doesn't actually work because we were comparing the values directly instead of going through stringMatches.

The types of the `value` and `placeholder` filters allow both a string and a regex, but passing in a regex doesn't actually work because we were comparing the values directly instead of going through `stringMatches`.
@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release labels Jul 31, 2020
@crisbeto crisbeto requested a review from mmalerba as a code owner July 31, 2020 15:32
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 31, 2020
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

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

LGTM

@mmalerba mmalerba added lgtm action: merge The PR is ready for merge by the caretaker and removed lgtm labels Jul 31, 2020
@wagnermaciel wagnermaciel merged commit 20e5ea9 into angular:master Aug 19, 2020
wagnermaciel pushed a commit that referenced this pull request Aug 19, 2020
The types of the `value` and `placeholder` filters allow both a string and a regex, but passing in a regex doesn't actually work because we were comparing the values directly instead of going through `stringMatches`.

(cherry picked from commit 20e5ea9)
@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 Sep 19, 2020
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 cla: yes PR author has agreed to Google's Contributor License Agreement P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants