Add writing direction to locale files#33556
Conversation
|
If you're wondering the purpose of this PR, it is to eventually support angular/angular-cli#16047 |
petebacondarwin
left a comment
There was a problem hiding this comment.
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
|
@petebacondarwin do you suggest I rebase this change on top of #33523? |
|
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 |
|
I've marked this as |
|
I noticed that #33523 was merged in. I guess I'll rebase this PR on top of master. |
|
Thanks @doom777 - sorry I didn't get back to you earlier. |
|
This is now competing with #33584 since they will also conflict :-/ |
|
@petebacondarwin true, but my PR was here first ;-) Edit: they are also merged with #33523 |
|
The question is really whether this can go into |
|
@petebacondarwin BTW, why are these locale files checked into source control? Why not generate them during the build process? |
|
That is a good question. It has been like this for many years. That being said we should look into ways to automate the update of these to some Bazel rules... |
|
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. |
|
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. |
|
blocked by: #33682 |
|
Hey, so we are in |
|
Sorry @doom777, the presubmits need to run again before merging. ETA 1-2 hours. |
There was a problem hiding this comment.
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 Thanks for that note. I have updated the code. Please review it. |
|
Hey, @IgorMinar @petebacondarwin can this PR move forward? |
|
Hey guys, just another ping on this PR. |
|
I'm afraid it is Thanksgiving in US - so it is unlikely anything will move on this before Tuesday. |
|
Hey, everyone. It's Tuesday here. Just pinging. |
IgorMinar
left a comment
There was a problem hiding this comment.
Lgtm now. Thank you for making all the follow up changes.
|
merge-assistance: global approval & caretaker can you please run presubmit? |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
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?
Other information
Look at first commit for actual changes. Second commit is just generated locale files