Reflection based Hero field/property fix #3
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
Without delegates, will require Harmony.Extension package, keeping it simple
zijistark
reviewed
Jul 2, 2021
|
|
||
| private delegate TextObject GetHeroNamePropertyDelegate(Hero instance); | ||
| private static readonly MethodInfo? GetHeroNameProperty = AccessTools.PropertyGetter(typeof(Hero), nameof(Hero.Name)); | ||
| private static readonly AccessTools.FieldRef<Hero, TextObject>? GetHeroNameField = AccessTools.FieldRefAccess<Hero, TextObject>("Hero"); |
There was a problem hiding this comment.
I think the string that would need to be passed into AccessTools.FieldRefAccess<,> is the name of the field (Name), not the class as it is here (Hero).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Without delegates, will require Harmony.Extension package, keeping it simple
Fixes #2