Skip to content
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

refactor(material/sort): explicit sort direction #23632

Merged

Conversation

lekhmanrus
Copy link
Contributor

Not sure if that is really needed.
Just it feels like it is more consistent with existing SortDirection. 🙂

@lekhmanrus lekhmanrus requested review from andrewseguin and a team as code owners September 24, 2021 00:47
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Sep 24, 2021
@josephperrott josephperrott removed the request for review from a team September 24, 2021 15:37
@lekhmanrus lekhmanrus force-pushed the explicit-sort-direction-type branch from 924a148 to cb472c8 Compare October 1, 2021 15:41
@lekhmanrus
Copy link
Contributor Author

Is there a way to restart ci/circleci: tests_browserstack test?

@josephperrott
Copy link
Member

@lekhmanrus I have triggered a rerun of the failing test.

@lekhmanrus lekhmanrus force-pushed the explicit-sort-direction-type branch from cb472c8 to e54f1fc Compare November 20, 2021 00:51
@lekhmanrus
Copy link
Contributor Author

Looks like the failing test is unrelated to the change. Could we rerun it again, please?

@andrewseguin andrewseguin removed the cla: yes PR author has agreed to Google's Contributor License Agreement label Dec 28, 2021
@lekhmanrus lekhmanrus force-pushed the explicit-sort-direction-type branch from e54f1fc to 18aa02e Compare February 5, 2022 00:00
@lekhmanrus lekhmanrus requested a review from crisbeto February 5, 2022 00:17
@andrewseguin andrewseguin added the target: patch This PR is targeted for the next patch release label Apr 21, 2022
@andrewseguin andrewseguin added the action: merge The PR is ready for merge by the caretaker label Apr 21, 2022
@andrewseguin
Copy link
Contributor

I can't remember if we wanted these to explicitly NOT be the empty string, but I can't think of a good enough justification now for it

@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 May 23, 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 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