Refactor ObjectExtensions -> ObjectMarshal #3760
Merged
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.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
All the
object
helpers are exposed as extensions through theObjectExtensions
class. These methods are all pretty dangerous and should only be used in very specific scenarios, but having them as extensions (and onobject
too) means they pop up in IntelliSense everywhere, as soon as a consumer references theMicrosoft.Toolkit.HighPerformance
package. This is not ideal and could be confusing for consumers, or at least just make the IntelliSense window more crowded for no real benefit.What is the new behavior?
The
object
extensions have been moved to a static helper classObjectMarshal
, and they're no longer extensions.PR Checklist
Please check if your PR fulfills the following requirements:
Pull Request has been submitted to the documentation repository instructions. Link:Sample in sample app has been added / updated (for bug fixes / features)Icon has been created (if new sample) following the Thumbnail Style Guide and templates