[feature/damAnalyzer] Remove reflection access patterns from tests #2444
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.
Removes the
RecodnizedReflectionAccessPattern
andUnrecognizedReflectionAccessPattern
attributes and all of the infrastructure for it.In the tests this is replaced by:
ExpectedNoWarning
on the test level which makes sure we don't produce unexpected warnings (basically equivalent toRecognizedReflecitonAccessPattern
.ExpectedWarning
to mark the places where warning should be generated - direct replacement forUnrecognizedReflectionAccessPattern
.This change also removes some of the test-private helpers and replaces it with the
DataFlowTypeExtensions
helpers.This is mostly a mechanical change.
This is part of the work to remove reflection access patterns from everywhere - in order to make the data flow logic sharable with the analyzer.