Fix & Enhancements for AddExplicitTypeToParameter
#926
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.
As promised in #917: Fix for
AddExplicitTypeToParameter
And some enhancements
Fix:
AddExplicitTypeToParameter
triggers despite type already specifiedEnhancement: Trigger for primary constructor
new (...) = ...
) already workedEnhancement: Surround with parens less often
,
and spaces somewhere between are ok:Fix:
NamedText.TryGetChar
throws exception when Position in last columnhmpf...no code in footnotes allowed
-> footnote substitute using custom separator, html and [*1]....
[*1]: Actually there were some more cases it didn't add parens: when other text directly adjacent to identifier and no spaces to next parens:
=>
But any spaces inside parens and param gets parens:
=>
With this PR neither of these cases gets parens