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

Adopt localize2 in more spots #204030

Merged
merged 2 commits into from Feb 2, 2024
Merged

Adopt localize2 in more spots #204030

merged 2 commits into from Feb 2, 2024

Conversation

mjbvz
Copy link
Contributor

@mjbvz mjbvz commented Feb 1, 2024

Another pass adopting localize2

Another pass adopting localize2
@mjbvz mjbvz enabled auto-merge (squash) February 1, 2024 20:51
@mjbvz mjbvz self-assigned this Feb 1, 2024
@VSCodeTriageBot VSCodeTriageBot added this to the February 2024 milestone Feb 1, 2024
Tyriar
Tyriar previously approved these changes Feb 1, 2024
@mjbvz mjbvz merged commit 7923151 into microsoft:main Feb 2, 2024
6 checks passed
joaomoreno added a commit that referenced this pull request Feb 2, 2024
joaomoreno added a commit that referenced this pull request Feb 2, 2024
Revert "Adopt localize2 in more spots (#204030)"

This reverts commit 7923151.
*
* This lets you explicitly pass in unlocalized strings to places that normally expect localized strings.
*/
export function unlocalized2(str: string): ILocalizedString {
Copy link
Member

Choose a reason for hiding this comment

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

This change needs to be done in the nls.build file as well. That's likely what caused the build failures

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants