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

feat(paginator): Use en dash in MatPaginatorIntl #16693

Merged
merged 1 commit into from
Sep 4, 2019
Merged

feat(paginator): Use en dash in MatPaginatorIntl #16693

merged 1 commit into from
Sep 4, 2019

Conversation

paulferaud
Copy link
Contributor

@paulferaud paulferaud commented Aug 6, 2019

Number ranges should be formatted with en dash.

Technically, there should be no spaces either: https://www.thepunctuationguide.com/en-dash.html
But since this isn’t a sentence, I think the spaces are fine (It’s also a less disruptive change, while still going in the right direction).

BREAKING CHANGE: MatPaginatorIntl will now cause MatPaginator to display
an 'EN DASH' (U+2013) rather than a 'HYPHEN-MINUS' (U+002D)

This is the correct typography to use to format number ranges

BREAKING CHANGE: MatPaginatorIntl will now cause MatPaginator to display
an 'EN DASH' (U+2013) rather than a 'HYPHEN-MINUS' (U+002D)
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 6, 2019
@paulferaud paulferaud marked this pull request as ready for review August 6, 2019 02:03
@paulferaud paulferaud changed the title feat: Use en dash in MatPaginatorIntl feat(paginator): Use en dash in MatPaginatorIntl Aug 6, 2019
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.

Seems reasonable to me, but I can see it triggering a bunch of screenshot test failures. Leaving it up to @jelbourn and @andrewseguin for final approval.

@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 Aug 6, 2019
@jelbourn jelbourn added the G This is is related to a Google internal issue label Aug 8, 2019
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

We'll see how breaking it ends up being.

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 8, 2019
@mmalerba
Copy link
Contributor

This results in ~100 targets failing, a combination of screen diffs and unit tests comparing against strings like '1 - 2'

@mmalerba mmalerba added the presubmit failures This PR has failures in Google's internal presubmit process and cannot be immediately merged label Aug 12, 2019
@jelbourn jelbourn added P4 A relatively minor issue that is not relevant to core functions and removed P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent labels Aug 13, 2019
@jelbourn
Copy link
Member

Since it causes so many breakages, this probably won't get merged for a long time (unless you want to do the work of getting it green inside Google, @paulferaud)

@paulferaud
Copy link
Contributor Author

@jelbourn As in just getting all tests inside Google in a state where they would pass with or without this change? Or is there a more manageable process?

I don’t think I can single single handedly fix 100 tests in such a way...

@jelbourn
Copy link
Member

For that many, yes, it would probably be getting affected the tests to pass either way and then also updating the screenshots affected. It's ultimately a lot of work for a small change.

@paulferaud
Copy link
Contributor Author

Alright. Would be nice to get this in eventually.

Hopefully, we could migrate a log of people to use the newer Xap paginator, which would alleviate the breakage.

@andrewseguin andrewseguin merged commit dd37ca5 into angular:master Sep 4, 2019
@andrewseguin
Copy link
Contributor

Took quite a lot of test and screenshot changes but we got a passing test run 👍

@paulferaud
Copy link
Contributor Author

That’s amazing! I was ready to give up on this. Thanks a lot!

PS: I saw the CL. Glad we could do this as a 1 shot.

@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 11, 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 G This is is related to a Google internal issue P4 A relatively minor issue that is not relevant to core functions presubmit failures This PR has failures in Google's internal presubmit process and cannot be immediately merged target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants