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

Merge main to main-vs-deps #54405

Merged
28 commits merged into from
Jun 27, 2021
Merged

Merge main to main-vs-deps #54405

28 commits merged into from
Jun 27, 2021

Conversation

dotnet-bot
Copy link
Collaborator

This is an automatically generated pull request from main into main-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/main-to-main-vs-deps
git reset --hard upstream/main-vs-deps
git merge upstream/main
# Fix merge conflicts
git commit
git push upstream merges/main-to-main-vs-deps --force

ryzngard and others added 28 commits June 16, 2021 21:13
Co-authored-by: David Wengier <david.wengier@microsoft.com>
Speed up progression searches by using the navigate-to index
…avigation

Value tracking originally used the standard WPF navigation pattern. This would also navigate to the source line based on selection.

This improves the design by manually handling keyboard navigation for most cases. By default, if an item is selected it no longer navigates to source. There are conditions where this is different:

| Shortcut | Expand Behavior | Navigates To Source | Previous or Next |
| --------- | ---------------- | ---------------------- | --------------------- |
| Arrow Down | False | True| Next |
| Arrow Up | False | True| Next |
| Arrow Left | Collapse Only | False | Neither |
| Arrow Right | Expand Only | False | Neither |
| Space | Toggle | False | Neither |
| Enter | False | True | Neither |
| F8 | Expand Only | True | Next |
| Shift + F8 | False | True | Previous |
| Click | False | True| Neither |
| Double Click | False | True | Neither |
Co-authored-by: David Wengier <david.wengier@microsoft.com>
Thread cancellation tokens through progression in more places.
@dotnet-bot dotnet-bot requested review from a team as code owners June 26, 2021 00:02
Copy link

@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

@ghost ghost merged commit c1a11ab into main-vs-deps Jun 27, 2021
@ghost ghost added this to the Next milestone Jun 27, 2021
@ghost ghost deleted the merges/main-to-main-vs-deps branch June 27, 2021 08:01
@RikkiGibson RikkiGibson modified the milestones: Next, 17.0.P2 Jun 29, 2021
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants