You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This pull request addresses a variable naming collision issue in the generated mock setup code, ensuring that local variables do not conflict with method parameter names. It also adds a test to verify that methods with parameters named setup or methodSetup compile correctly.
Fixes for variable naming collisions in generated code:
Updated AppendMethodSetupImplementation in Sources.MockClass.cs to generate unique local variable names for method setup variables, preventing conflicts with parameter names.
Replaced hardcoded "methodSetup" variable names with a unique name throughout the method setup code, including in return statements and registry setup calls.
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
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 pull request addresses a variable naming collision issue in the generated mock setup code, ensuring that local variables do not conflict with method parameter names. It also adds a test to verify that methods with parameters named
setupormethodSetupcompile correctly.Fixes for variable naming collisions in generated code:
AppendMethodSetupImplementationinSources.MockClass.csto generate unique local variable names for method setup variables, preventing conflicts with parameter names."methodSetup"variable names with a unique name throughout the method setup code, including in return statements and registry setup calls.