Skip to content

fix cdata formatting #2893

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

Merged
merged 1 commit into from
Jul 31, 2019
Merged

fix cdata formatting #2893

merged 1 commit into from
Jul 31, 2019

Conversation

mairaw
Copy link
Contributor

@mairaw mairaw commented Jul 31, 2019

Found a few more. I'm wondering if this the porting tool that is doing this formatting @carlossanlop?

@mairaw mairaw added this to the August 2019 milestone Jul 31, 2019
@mairaw mairaw requested review from carlossanlop and rpetrusha July 31, 2019 05:51
@mairaw mairaw self-assigned this Jul 31, 2019
@mairaw mairaw added the loc Indicates issues that are about localized content label Jul 31, 2019
@mairaw mairaw merged commit a61a79d into dotnet:master Jul 31, 2019
@mairaw mairaw deleted the cdata branch July 31, 2019 07:24
@carlossanlop
Copy link
Contributor

@mairaw no, on the contrary, my tool has been fixing these. If you look at my latest batch of Json PRs, my tool made the same fixes you made here. Which leads me to think that the files get bad at some point after I submit my PR.

@carlossanlop
Copy link
Contributor

Update: Apparently my tool did this. The PR that had all these System.Text.Json comments was submitted many weeks ago, back when this bug was not fixed yet. I got the issue fixed in my tool a couple of weeks ago (when we were first notified by the Loc team about this problem).

I'll double check my recent Json PRs to make sure we don't do the same issue.

@mairaw
Copy link
Contributor Author

mairaw commented Jul 31, 2019

Great, thanks @carlossanlop!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
loc Indicates issues that are about localized content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants