Provide implementation-side visualization (per request), and always show raw data #1128
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
Scottj1s
commented
Mar 24, 2022
| Class, | ||
| }; | ||
|
|
||
| enum class ObjectType |
Member
Author
There was a problem hiding this comment.
this change from bool can be ignored - thought I'd need a tri-state for implementations, but just decided to keep it.
the only real meat is winrt::impl::producer addition and removing the condition on expanding (which permits raw data to always be visible)
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.
Added visualization for winrt::impl::producer<...> subclasses (implementations), per several requests
Always show raw data, for classes that inherit IInspectable but metadata is not available