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

I18n - compile time inlining #32881

Closed

Conversation

petebacondarwin
Copy link
Member

@petebacondarwin petebacondarwin commented Sep 27, 2019

No description provided.

@petebacondarwin petebacondarwin added action: review The PR is still awaiting reviews from at least one requested reviewer area: i18n target: major This PR is targeted for the next major release comp: ivy labels Sep 27, 2019
@ngbot ngbot bot added this to the needsTriage milestone Sep 27, 2019
@petebacondarwin petebacondarwin mentioned this pull request Sep 27, 2019
14 tasks
@petebacondarwin petebacondarwin force-pushed the i18n-compile-time branch 6 times, most recently from 13aa1f1 to 97aee88 Compare September 30, 2019 12:18
@petebacondarwin petebacondarwin force-pushed the i18n-compile-time branch 2 times, most recently from 50f4f23 to 5332292 Compare October 3, 2019 21:07
@petebacondarwin petebacondarwin marked this pull request as ready for review October 3, 2019 21:10
@petebacondarwin petebacondarwin requested review from a team as code owners October 3, 2019 21:10
@petebacondarwin petebacondarwin force-pushed the i18n-compile-time branch 2 times, most recently from e6b796d to 39559c9 Compare October 4, 2019 08:27
@AndrewKushnir
Copy link
Contributor

AndrewKushnir commented Oct 5, 2019

@petebacondarwin FYI I'm in the process of reviewing this PR, will let you know once it's completed (most likely Monday, 10/7). Thank you.

@petebacondarwin
Copy link
Member Author

Thanks Andrew. I am going to tweak the API a bit, today, after discussions with @alan-agius4. But I will add the changes as fixup commits so that it doesn't affect your review if you are going commit by commit.

@petebacondarwin petebacondarwin force-pushed the i18n-compile-time branch 3 times, most recently from ee238ab to 6ca46a9 Compare October 7, 2019 07:34
Copy link
Contributor

@AndrewKushnir AndrewKushnir left a comment

Choose a reason for hiding this comment

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

Very impressive work @petebacondarwin! 👍
I left a few minor comments, none of them are blockers.
Thank you.

@AndrewKushnir
Copy link
Contributor

FYI, VE and Ivy presubmits are successful. Thank you.

@AndrewKushnir AndrewKushnir removed the action: presubmit The PR is in need of a google3 presubmit label Oct 8, 2019
This commit implements a tool that will inline translations and generate
a translated copy of a set of application files from a set of translation
files.
Copy link
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.

I did a high level review of the PR (general architecture, public api, docs, tests) but didn't check all the details - I'm relying on other reviewers for that.

everything looks good, except for the missing license for babel__core types. Can you please fix that - you can create a new license.md file if one doesn't exist in the original repo, as long as you populate it with the correct licensing info. thanks!

const templateBuilder: DefaultTemplateBuilder;

export default templateBuilder;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

can you please ensure that these typings files don't end up in the built npm packages?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure how to configure the Bazel rules to do that...

Copy link
Member

Choose a reason for hiding this comment

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

I'm not either, unfortunately. That would be a good @alexeagle question. I don't know how npm_package determines the set of files to include.

Do references to these types end up in the .d.ts files for the package? If so, it might be very difficult to get the package build to exclude them.

Copy link
Member Author

Choose a reason for hiding this comment

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

Instead I suggest that we just try to get bazelbuild/rules_nodejs#1033 fixed, which will allow us to remove these typings files altogether.

How about we land this PR now and then work to fix that issue and remove the typings before RC?

Copy link
Member

Choose a reason for hiding this comment

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

Per Igor, this is the approach we'll take. I will merge this PR soon.

Copy link
Contributor

Choose a reason for hiding this comment

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

@petebacondarwin Is there a Jira for this? Who is working on the Bazel fixes?

Copy link
Member Author

Choose a reason for hiding this comment

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

@alexeagle is working on the fix as part of the Bazel team. I don't know if there is a JIRA for it. There is not one in the FW JIRA.

@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 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 Oct 8, 2019
@ngbot
Copy link

ngbot bot commented Oct 8, 2019

I see that you just added the PR action: merge label, but the following checks are still failing:
    failure status "ci/angular: size" is failing
    failure status "ci/circleci: build-ivy-npm-packages" is failing
    failure status "ci/circleci: build-npm-packages" is failing
    failure status "ci/circleci: test" is failing
    failure status "ci/circleci: test_ivy_aot" is failing
    pending forbidden labels detected: PR action: cleanup
    pending status "google3" is pending
    pending missing required status "ci/circleci: publish_snapshot"

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

@IgorMinar
Copy link
Contributor

hmm.. and ci seems to be failing due to duplicate dependencies? @petebacondarwin can you please take a look?

@petebacondarwin
Copy link
Member Author

@IgorMinar - @babel/core typings LICENSE file added

@alxhub alxhub removed the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label Oct 9, 2019
@alxhub alxhub closed this in 2cdb3a0 Oct 9, 2019
alxhub pushed a commit that referenced this pull request Oct 9, 2019
…32881)

This closer reflects what caused the error.

PR Close #32881
@petebacondarwin petebacondarwin deleted the i18n-compile-time branch October 9, 2019 20:28
ODAVING pushed a commit to ODAVING/angular that referenced this pull request Oct 18, 2019
This commit implements a tool that will inline translations and generate
a translated copy of a set of application files from a set of translation
files.

PR Close angular#32881
ODAVING pushed a commit to ODAVING/angular that referenced this pull request Oct 18, 2019
@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 Nov 10, 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 area: i18n cla: yes target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants