-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Multiple assigns to TagAction for Msg #3966
Comments
Yes, we should. A sanity check for duplicate tags (at least logging a warning) might be prudent. |
Yeah totally agree here. My gut tells me the baseapp should continue to perform its role in adding the action tag -- this provides less things to worry about in each handler and requires less docs update. |
how are this tags useful if they don't involve any transaction (i.e they are not queryable)? Should we get rid of them ?
|
also what's a |
@fedekunze we should do a sweep through and see what tags are not used anymore and why they're not used. Remove the ones that you deem useless.
|
Just noticed that many of the modules use the action tag, but also the action tag is appended for each message within baseapp (here https://github.com/cosmos/cosmos-sdk/blob/develop/baseapp/baseapp.go#L690)
We should consolidate so either modules don't use the action tag for each message, or baseapp doesn't append an action tag
Additionally, the spec tag sections must be updated if we go with the latter choice.
CC @jackzampolin @cwgoes @alexanderbez
Relevant search:
The text was updated successfully, but these errors were encountered: