Skip to content

Update CS1935 compiler message text to remove System.Core.dll reference#45920

Merged
AlekseyTs merged 2 commits intodotnet:masterfrom
kfechter:master
Jul 15, 2020
Merged

Update CS1935 compiler message text to remove System.Core.dll reference#45920
AlekseyTs merged 2 commits intodotnet:masterfrom
kfechter:master

Conversation

@kfechter
Copy link
Contributor

Fixes #37165

Changes the using reference portion of the CS1935 message from 'Are you missing a reference to 'System.Core.dll' or a using directive for 'System.Linq'?' to 'Are you missing a using directive for 'System.Linq'?' and removes the references in all the comments and associated tests.

@kfechter kfechter requested a review from a team as a code owner July 11, 2020 22:08
@RikkiGibson RikkiGibson added Area-Compilers Concept-Diagnostic Clarity The issues deals with the ease of understanding of errors and warnings. Community The pull request was submitted by a contributor who is not a Microsoft employee. labels Jul 11, 2020
Copy link
Member

@RikkiGibson RikkiGibson left a comment

Choose a reason for hiding this comment

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

Looks good, thanks!

@RikkiGibson RikkiGibson requested a review from a team July 11, 2020 22:41
@kfechter
Copy link
Contributor Author

Looks good, thanks!

No problem. I do have one question. The non English localization files were updated automatically when the resource file was changed. As I am not fluent enough in the languages to ensure the localizations are correct, what is the best way to ensure that all of the localization files are updated/reviewed accordingly?

@AlekseyTs
Copy link
Contributor

AlekseyTs commented Jul 12, 2020

As I am not fluent enough in the languages to ensure the localizations are correct, what is the best way to ensure that all of the localization files are updated/reviewed accordingly?

Don't worry about this, the files are automatically modified to make sure translators review the changes and make appropriate adjustments. #Closed

@333fred
Copy link
Member

333fred commented Jul 12, 2020

As I am not fluent enough in the languages to ensure the localizations are correct, what is the best way to ensure that all of the localization files are updated/reviewed accordingly?

If we were required to be fluent enough in all those languages to do translations, I think we would all lose our jobs 😅

@kfechter
Copy link
Contributor Author

As I am not fluent enough in the languages to ensure the localizations are correct, what is the best way to ensure that all of the localization files are updated/reviewed accordingly?

If we were required to be fluent enough in all those languages to do translations, I think we would all lose our jobs 😅

haha, that's fair. Guess I really only needed to ask if there was anything specific I had to do in that regard.

<value>Could not find an implementation of the query pattern for source type '{0}'. '{1}' not found. Consider explicitly specifying the type of the range variable '{2}'.</value>
</data>
<data name="ERR_QueryNoProviderStandard" xml:space="preserve">
<value>Could not find an implementation of the query pattern for source type '{0}'. '{1}' not found. Are you missing a reference to 'System.Core.dll' or a using directive for 'System.Linq'?</value>
Copy link
Contributor

@AlekseyTs AlekseyTs Jul 14, 2020

Choose a reason for hiding this comment

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

reference to 'System.Core.dll' or a [](start = 125, length = 36)

Should we still mention references, but without any specific names? Something like: "Are you missing references to required assemblies or a using directive for 'System.Linq'?" #Closed

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's a fair point.

I don't see any issues adding that information to the message. mentioning the reference assemblies but not specific names might make it more clear then just mentioning the using. I can make that change here in a bit.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Got a bit sidetracked with work, but I just added this commit.
7a96e07

it changes the message to "Are you missing required assembly references or a using directive for 'System.Linq'?"

@AlekseyTs
Copy link
Contributor

AlekseyTs commented Jul 14, 2020

Done with review pass (iteration 1) #Closed

Copy link
Contributor

@AlekseyTs AlekseyTs left a comment

Choose a reason for hiding this comment

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

LGTM (iteration 2), assuming CI is passing.

@AlekseyTs
Copy link
Contributor

@kfechter Would it be fine if we squash commits in the process of merging this PR?

@kfechter
Copy link
Contributor Author

@kfechter Would it be fine if we squash commits in the process of merging this PR?

yeah, I don't have any issues with that.

@AlekseyTs AlekseyTs merged commit f39e321 into dotnet:master Jul 15, 2020
@ghost ghost added this to the Next milestone Jul 15, 2020
@AlekseyTs
Copy link
Contributor

@kfechter Thanks for the contribution.

@JoeRobich JoeRobich modified the milestones: Next, 16.8.P1 Jul 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Compilers Community The pull request was submitted by a contributor who is not a Microsoft employee. Concept-Diagnostic Clarity The issues deals with the ease of understanding of errors and warnings.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CS1935 message is misleading

5 participants