This repository has been archived by the owner on Jun 30, 2023. It is now read-only.
Added support for custom mocks #16
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
A new analyzer provides additional "Implement stunt" and "Implement though behavior pipeline" code fixes for built-in interface and abstract class missing implementation diagnostics, which allows you to manually create mocks/stunts in whatever namespace you want, with whichever interfaces you want. This feature supports advanced custom mocking scenarios by giving the user full control of the code generation. The underlying processors were refactored a bit to allow more granular control and reusability for this scenario, such as extracing the default imports into its own processor `DefaultImports.cs`, and the core IStunt interface implementation into its own `CSharpStunt.cs` and `VisualBasicStunt.cs`. Generator method type arguments validation has also been added as analyzers so we can detect this invalid scenario even before trying to generate code for it.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
A new analyzer provides additional "Implement stunt" and "Implement though
behavior pipeline" code fixes for built-in interface and abstract class
missing implementation diagnostics, which allows you to manually create
mocks/stunts in whatever namespace you want, with whichever interfaces
you want.
This feature supports advanced custom mocking scenarios by giving the user
full control of the code generation.
The underlying processors were refactored a bit to allow more granular
control and reusability for this scenario, such as extracing the default
imports into its own processor
DefaultImports.cs, and the core IStuntinterface implementation into its own
CSharpStunt.csandVisualBasicStunt.cs.Generator method type arguments validation has also been added as analyzers
so we can detect this invalid scenario even before trying to generate code
for it.