docs: rename ng xi18n to ng extract-i18n - #39337

@petebacondarwin the above command will need to be changed in the future, the current CLI on npm doesn't contain the new command name.

@petebacondarwin pushed

@alan-agius4 @petebacondarwin I was wondering if there is a chance that we may need to add more i18n-related scripts to CLI? If I remember correctly Pete mentioned a migration tool/script to convert legacy message ids to new format (we don't have it, but may consider adding it in the future). If we plan to add more scripts, make be we can take that into account and format the command like this:

ng i18n:extract
ng i18n:<subcommand>

or

ng i18n-extract
ng i18n-<subcommand>

What do you think? May be we already have similar APIs in CLI?

Thank you.

@AndrewKushnir, initially we were going for ng i18n-extract but we realised that currently the builder and the key defined in the users project angular.json is already set to extract-i18n. In order to avoid users from being confused we decided the align everything and go for extract-i18n.

When it comes to migration tool, this to me sounds like it should fall under ng update and shouldn't add added as a separate command.

That being said, at the moment we do have a sub-command pattern in the CLI like:

ng generate component
ng generate app-shell

But then again the infra-structure currently only works for the ng generate.

In general if a command will not be used frequently on can opt to use ng run instead of ng command.

Example:

ng run my-application:server:production

The above is how a server bundle is build because there is no command to build a server application like (ng server).

That being said most ng commands can be configured and "mapped" by the users. Example, a user can choose that ng build will be mapped to building server application instead of the browser application, or to use a 3rd party builder which builds their application as an electron wrapped application.

This also means, that the users can change the mapping of ng extract-i18n (If there is a tool out there that can extract i18n from Angular templates) or maybe create a new builder that wraps the official one, and add functionality on top of that.

Caretaker: I don't think this requires a g3 pre-submit. Feel free to run it if you think otherwise. Thanks.

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.}