fix(ivy): use globally unique names for i18n constants (#25689)
Closure compiler requires that the i18n message constants of the form const MSG_XYZ = goog.getMessage('...'); have names that are unique across an entire compilation, even if the variables themselves are local to a given module. This means that in practice these names must be unique in a codebase. The best way to guarantee this requirement is met is to encode the relative file name of the file into which the constant is being written into the constant name itself. This commit implements that solution. PR Close #25689
This commit is contained in:

committed by
Misko Hevery

parent
bd0eb0d1d4
commit
cc29b9cf93
@ -127,6 +127,13 @@ export interface R3ComponentMetadata extends R3DirectiveMetadata {
|
||||
* Selectors found in the <ng-content> tags in the template.
|
||||
*/
|
||||
ngContentSelectors: string[];
|
||||
|
||||
/**
|
||||
* Path to the .ts file in which this template's generated code will be included, relative to
|
||||
* the compilation root. This will be used to generate identifiers that need to be globally
|
||||
* unique in certain contexts (such as g3).
|
||||
*/
|
||||
relativeContextFilePath: string;
|
||||
};
|
||||
|
||||
/**
|
||||
|
Reference in New Issue
Block a user