Adding various extensions to expose APIs in a object oriented manner. #31
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. Do you have a stylistic preference of keeping things on two lines when using the => syntax? I feel like keeping it on one line is easier on the eyes. Let me know, but besides that personal preference LGTM. |
|
I mostly just did it for consistency. There are some lines which might be too long to keep on a single line, and so I just did everything on two. I don't have much personal preference here either, so I can fix if you want. |
|
Updated to be single line. |
mjsabby
approved these changes
Apr 23, 2019
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.
This is, overall, still a WIP. However, this is an initial push of changes to expose the P/Invoke APIs in a more object oriented manner. This improves discoverability and usage.