Skip to content

cleanup: restructure select harness to follow the same file structure as other harnesses #17120

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 2 commits into from
Sep 18, 2019

Conversation

mmalerba
Copy link
Contributor

The select harness should remain in experimental until the form-field
harness is developed.

other harnesses

The select harness should remain in experimental until the form-field
harness is developed.
@mmalerba mmalerba added pr: merge safe target: major This PR is targeted for the next major release labels Sep 17, 2019
@mmalerba mmalerba requested a review from jelbourn September 17, 2019 21:34
@mmalerba mmalerba requested a review from crisbeto as a code owner September 17, 2019 21:34
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 17, 2019
@mmalerba mmalerba requested a review from a team as a code owner September 17, 2019 22:31
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

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

LGTM. This would be needed for #17138 as it creates a real entry-point that can be imported from other harnesses.

@mmalerba mmalerba added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Sep 18, 2019
@mmalerba mmalerba merged commit 7b73ea5 into angular:master Sep 18, 2019
@mmalerba mmalerba deleted the mv-select-harness branch September 18, 2019 20:21
@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 Oct 19, 2019
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 target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants