Alter reset and input names when they conflict #429
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.
Fixes #427
Very rarely, the generated names for resetting optional values and accessing the input value for required or optional values conflicts with other values.
I checked nearly 400 providers and found only 3 instances of conflict with
reset
and 1 withinput
. As such, I choose to only diverge from convention when necessary rather than changing the naming overall.XInput
->XTfInput
andresetX
->resetTfX