docs: use documentation tags where appropriate #130
Merged
Conversation
This file contains 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
love it!
eaddingtonwhite
approved these changes
Aug 30, 2022
There was a problem hiding this comment.
Wow interesting did not know you could do this w/ c#. TIL c# suprises me in new ways every day. :) This looks cleaner/easier to maintain to me! Nice work! we should make sure to double check in IDE as well make sure all looks good to end user w/ this new approach.
|
I verified in VS Code but we should followup in Visual Studio and Rider as well. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Use the breadth of .NET documentation tags where appropriate. The previous code had markdown in places which will not display correctly in Intellisense.
This also reduces a lot of copy-paste documentation by using
inheritdoc.Closes #127