Update readme for 1.3 #597
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
Addresses #578 |
Contributor
|
@DustinCampbell I was just comping you an email about this. Great minds think alike :). I will send you some text. |
Member
Author
|
Also addresses #553 |
Member
Author
|
OK, I added the debugger what's new items. I reworded some of the text a bit, so please take a look. |
Member
Author
|
Also, I arbitrarily ordered them to highlight some of the more important items. Let me know if you disagree with the order and I'll change it. |
| * Support for conditional breakpoints | ||
| * New configuration option to enable [stepping into properties and operators](https://github.com/OmniSharp/omnisharp-vscode/blob/release/debugger.md#stepping-into-properties-and-operators). | ||
| * Duplicate warnings and errors should no longer accumulate in Unity projects [#447](https://github.com/OmniSharp/omnisharp-vscode/issues/447) | ||
|
|
Contributor
There was a problem hiding this comment.
Two other debugger items that I realized I forgot --
- Support for setting the value of variables in the debugger. To do this, right click on the variable and invoke 'Set Value'.
- Display of type names for variables changed in the debugger to support VS Code's variable assignments. A shortened form of the type names is now displayed as part of the variable name, and the full type name can be viewed by hovering over the name.
Contributor
|
Otherwise LGTM |
Contributor
|
👍 |
Member
Author
|
@gregg-miskelly: Does this look right? These two items appeared to me to be related, so I collapsed them. Was that correct? |
Member
Author
|
ping? |
Contributor
|
LGTM |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@gregg-miskelly, @caslan: If you send me information for the debugger, I'll incorporate it into this PR.