An issue was discovered in the GetActor function defined in actor.go. Specifically, when the actorType input argument matches with types.ValidatorActor.GetActorType(), the schema variable is currently assigned as types.FishermanActor. This appears to be a typo or error, as logically schema should be assigned types.ValidatorActor in this case. This could potentially cause GetActor to behave unexpectedly when called with types.ValidatorActor.GetActorType() as it would process as if it were types.FishermanActor.GetActorType().
Proposed Fix:
This pull request corrects the schema assignment for types.ValidatorActor.GetActorType() from types.FishermanActor to types.ValidatorActor, thus aligning the function behavior with the expected logic.
Issue:
An issue was discovered in the
GetActorfunction defined inactor.go. Specifically, when theactorTypeinput argument matches withtypes.ValidatorActor.GetActorType(), theschemavariable is currently assigned astypes.FishermanActor. This appears to be a typo or error, as logicallyschemashould be assignedtypes.ValidatorActorin this case. This could potentially causeGetActorto behave unexpectedly when called withtypes.ValidatorActor.GetActorType()as it would process as if it weretypes.FishermanActor.GetActorType().Proposed Fix:
This pull request corrects the
schemaassignment fortypes.ValidatorActor.GetActorType()fromtypes.FishermanActortotypes.ValidatorActor, thus aligning the function behavior with the expected logic.Type of change
Please mark the relevant option(s):