Skip to content

Add writing direction to locale files#33556

Closed
ghost wants to merge 2 commits intomasterfrom
unknown repository
Closed

Add writing direction to locale files#33556
ghost wants to merge 2 commits intomasterfrom
unknown repository

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented Nov 3, 2019

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Locale files do not contain writing direction

What is the new behavior?

Locale files will contain writing direction

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Look at first commit for actual changes. Second commit is just generated locale files

@ghost ghost requested review from a team November 3, 2019 13:37
@ghost ghost self-requested a review November 3, 2019 14:22
@ghost
Copy link
Copy Markdown
Author

ghost commented Nov 3, 2019

If you're wondering the purpose of this PR, it is to eventually support angular/angular-cli#16047
Currently, creating an RTL locale build does not make the page RTL

Copy link
Copy Markdown
Contributor

@petebacondarwin petebacondarwin left a comment

Choose a reason for hiding this comment

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

Thanks for this PR - generally looks good. A couple of items to look at.
We should also consider whether this should land before or after #33523 as they clearly conflict with each other.

I think also that since we are well into the RC now, and this has a public API change, then this will probably go into 9.1.0

@ghost
Copy link
Copy Markdown
Author

ghost commented Nov 4, 2019

@petebacondarwin do you suggest I rebase this change on top of #33523?

@petebacondarwin
Copy link
Copy Markdown
Contributor

Let's hold off for 24 hours while we work out what release this could go in and what to do about that other PR. Cheers

@petebacondarwin petebacondarwin added area: i18n Issues related to localization and internationalization target: major This PR is targeted for the next major release feature Label used to distinguish feature request from other issues labels Nov 4, 2019
@ngbot ngbot bot modified the milestone: needsTriage Nov 4, 2019
@petebacondarwin
Copy link
Copy Markdown
Contributor

I've marked this as target: master only as I think it might have to go into 9.1.x.
@IgorMinar do you have a view?

@petebacondarwin petebacondarwin self-assigned this Nov 4, 2019
Copy link
Copy Markdown
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM, for dev-infra

@ghost
Copy link
Copy Markdown
Author

ghost commented Nov 5, 2019

I noticed that #33523 was merged in. I guess I'll rebase this PR on top of master.

@petebacondarwin
Copy link
Copy Markdown
Contributor

Thanks @doom777 - sorry I didn't get back to you earlier.

@petebacondarwin petebacondarwin added action: presubmit The PR is in need of a google3 presubmit action: review The PR is still awaiting reviews from at least one requested reviewer labels Nov 6, 2019
@petebacondarwin
Copy link
Copy Markdown
Contributor

This is now competing with #33584 since they will also conflict :-/

@ghost
Copy link
Copy Markdown
Author

ghost commented Nov 6, 2019

@petebacondarwin true, but my PR was here first ;-)
Also, this PR is further ahead of the other one, since we got more approvals, and are merged with master.
Also, if you really insist, I can rebase this PR on top of that one also.

Edit: they are also merged with #33523

@petebacondarwin
Copy link
Copy Markdown
Contributor

The question is really whether this can go into master & patch (e.g. 9.0.0) or only master (e.g. 9.1.0), since it is arguably a new public API and we are now in RC for 9.0.0. cc @IgorMinar / @kara ?

@ghost
Copy link
Copy Markdown
Author

ghost commented Nov 6, 2019

@petebacondarwin BTW, why are these locale files checked into source control? Why not generate them during the build process?

@petebacondarwin
Copy link
Copy Markdown
Contributor

That is a good question. It has been like this for many years.
I think it is nice not to have to generate them locally when developing that Angular framework.

That being said we should look into ways to automate the update of these to some Bazel rules...

@josephperrott
Copy link
Copy Markdown
Member

This is actually an outstanding task for the @angular/dev-infra-framework team. To determine if continuing to store them in the repository is the best option or if they should be generated at build time. And with whichever method, how to best do that going forward.

@AndrewKushnir
Copy link
Copy Markdown
Contributor

Adding @IgorMinar to reviewers list, since there are changes to public API that need to be reviewed/approved. @IgorMinar, could you please have a look at the first commit (where the API changes are)? Thank you.

@ghost
Copy link
Copy Markdown
Author

ghost commented Nov 8, 2019

blocked by: #33682

@mhevery mhevery added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Nov 18, 2019
@ghost
Copy link
Copy Markdown
Author

ghost commented Nov 21, 2019

Hey, so we are in action:merge right now, so what else needs to be done?

@matsko
Copy link
Copy Markdown
Contributor

matsko commented Nov 21, 2019

Sorry @doom777, the presubmits need to run again before merging. ETA 1-2 hours.

@matsko
Copy link
Copy Markdown
Contributor

matsko commented Nov 21, 2019

Copy link
Copy Markdown
Contributor

@IgorMinar IgorMinar left a comment

Choose a reason for hiding this comment

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

Hi there, I rereviewed the PR again and noticed that getLocaleDirection is not reexported from @angular/core which means that the function is not available via the public api surface, rendering this feature inaccessible to developers (outside of our own unit tests).

Can you please update the PR with proper reexports, which will also trigger the need to update the public api guard (the CI failure will instruct you what command to run to do that).

While this PR is large, it should not conflict with other PRs, so we shouldn't rush to get it in because of a fear that it will bit rot. It's more important that we merge it in in a functional state.

@IgorMinar IgorMinar added action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews and removed action: merge The PR is ready for merge by the caretaker labels Nov 22, 2019
@ghost ghost self-requested a review November 22, 2019 10:16
@ghost
Copy link
Copy Markdown
Author

ghost commented Nov 22, 2019

@IgorMinar Thanks for that note. I have updated the code. Please review it.
Of course you're correct that it's more important that the PR is functional, then just merged.

@ghost
Copy link
Copy Markdown
Author

ghost commented Nov 25, 2019

Hey, @IgorMinar @petebacondarwin can this PR move forward?

@ghost
Copy link
Copy Markdown
Author

ghost commented Nov 28, 2019

Hey guys, just another ping on this PR.

@petebacondarwin
Copy link
Copy Markdown
Contributor

I'm afraid it is Thanksgiving in US - so it is unlikely anything will move on this before Tuesday.

@ghost
Copy link
Copy Markdown
Author

ghost commented Dec 3, 2019

Hey, everyone. It's Tuesday here. Just pinging.

@petebacondarwin petebacondarwin added action: review The PR is still awaiting reviews from at least one requested reviewer and removed action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews labels Dec 3, 2019
Copy link
Copy Markdown
Contributor

@IgorMinar IgorMinar left a comment

Choose a reason for hiding this comment

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

Lgtm now. Thank you for making all the follow up changes.

@IgorMinar IgorMinar added action: merge The PR is ready for merge by the caretaker merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note action: presubmit The PR is in need of a google3 presubmit and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Dec 3, 2019
@IgorMinar
Copy link
Copy Markdown
Contributor

IgorMinar commented Dec 3, 2019

merge-assistance: global approval & caretaker can you please run presubmit?

@mhevery
Copy link
Copy Markdown
Contributor

mhevery commented Dec 3, 2019

presubmit

@mhevery mhevery closed this in 3c24384 Dec 3, 2019
mhevery pushed a commit that referenced this pull request Dec 3, 2019
@angular-automatic-lock-bot
Copy link
Copy Markdown

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 Jan 3, 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 action: presubmit The PR is in need of a google3 presubmit area: i18n Issues related to localization and internationalization cla: yes feature Label used to distinguish feature request from other issues merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants