Skip to content

Merge master to master-vs-deps#51176

Merged
JoeRobich merged 47 commits intomaster-vs-depsfrom
merges/master-to-master-vs-deps
Feb 12, 2021
Merged

Merge master to master-vs-deps#51176
JoeRobich merged 47 commits intomaster-vs-depsfrom
merges/master-to-master-vs-deps

Conversation

@dotnet-bot
Copy link
Copy Markdown
Collaborator

This is an automatically generated pull request from master into master-vs-deps.

Once all conflicts are resolved and all the tests pass, you are free to merge the pull request. 🐯

Troubleshooting conflicts

Identify authors of changes which introduced merge conflicts

Scroll to the bottom, then for each file containing conflicts copy its path into the following searches:

Usually the most recent change to a file between the two branches is considered to have introduced the conflicts, but sometimes it will be necessary to look for the conflicting lines and check the blame in each branch. Generally the author whose change introduced the conflicts should pull down this PR, fix the conflicts locally, then push up a commit resolving the conflicts.

Resolve merge conflicts using your local repo

Sometimes merge conflicts may be present on GitHub but merging locally will work without conflicts. This is due to differences between the merge algorithm used in local git versus the one used by GitHub.

git fetch --all
git checkout merges/master-to-master-vs-deps
git reset --hard upstream/master-vs-deps
git merge upstream/master
# Fix merge conflicts
git commit
git push upstream merges/master-to-master-vs-deps --force

jasonmalinowski and others added 30 commits February 2, 2021 20:56
We are responsible for filling out the contents under the Analyzers
node where we put the list of analyzers, generators, and information
about them. To do this we have to go from an IVsHierarchy and item
in the Solution Explorer to a Roslyn project. Our code was trying to
take the IVsHierarchy and item to get a project path and TFM, and then
trying to walk through our projects to find a project associated with
the same project path and TFM. This code however was written back when
there was a wrapper hierarchy for each project in a multi-targeted
project which hasn't been the case for some time.

The project system is now passing us what is roughly a TFM through
IWorkspaceProjectContext which we can use to match up and select the
correct Roslyn Project in the multitargeting case.

Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1275676
The equality fo a DocumentId is defined by comparing the GUID of the
DocumentId and the GUID of the ProjectId, so it's already the case that
if we have two generated documents with the same hint path we'll end
up with different DocumentIds. However, if anybody tries getting
'clever' with the GUID of the DocumentId (or are just inspecting it
in a debugger) it might get confusing. This ensures they're different.

Fixes #50714
…ulti-targeting-handling

Fix source generator multi-targeting handling
Now that tree edits are computed for statement syntax, there is no guarantee nodes will be labelled
Fix suggestion mode when triggered with delete
@dotnet-bot dotnet-bot requested a review from a team as a code owner February 12, 2021 00:03
@dotnet-bot dotnet-bot added Area-Infrastructure auto-merge Merge Conflicts There are merge conflicts with the base branch. labels Feb 12, 2021
Copy link
Copy Markdown

@ghost ghost left a comment

Choose a reason for hiding this comment

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

Auto-approval

@dotnet-bot dotnet-bot requested review from a team as code owners February 12, 2021 04:20
@JoeRobich JoeRobich force-pushed the merges/master-to-master-vs-deps branch 3 times, most recently from af31ddd to 7d3f07c Compare February 12, 2021 17:37
@JoeRobich JoeRobich merged commit 7dfc335 into master-vs-deps Feb 12, 2021
@ghost ghost added this to the Next milestone Feb 12, 2021
@RikkiGibson RikkiGibson modified the milestones: Next, 16.10.P1 Feb 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-Infrastructure auto-merge Merge Conflicts There are merge conflicts with the base branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants