-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Trivial) Rename TxName
#5230
Comments
Hi @kevinrr888 myself Mrinmoy. First of all I want to ask is this issue already assigned to someone?? THANKS :) |
Hi @richochetclementine1315 Let me know if you would like me to assign this ticket to you. |
yes...I wanna work upon this issue @kevinrr888 :) |
@kevinrr888 I just did a PR.... Kindly take a look... please feel free to tell if some other changes are required. Thanks!! :) |
hi @kevinrr888... I've made the changes. Please take a look THANKS :) |
Is your feature request related to a problem? Please describe.
Prior to #5218, a String was passed around and stored representing the type of fate operation being performed. This was changed to be a concrete type.
TxName
and similar naming are still used throughout the FATE code, which isn't as representative of what is being passed/stored now.Describe the solution you'd like
All mentions of
TxName
or similar should be renamed to something more appropriate likefateOp
,txOp
,txOperation
, etc.The text was updated successfully, but these errors were encountered: