Skip to content
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

Add event aggregator function call in baseapp #268

Merged
merged 6 commits into from
Sep 30, 2022

Conversation

nullpointer0x00
Copy link

@nullpointer0x00 nullpointer0x00 commented Sep 29, 2022

Description

This is an optional function that allows for manipulation of the events that will be emitted from the baseapp.

This is to accomplish issue: provenance-io/provenance#1092

Closes: #XXXX


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • added ! to the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • followed the guidelines for building modules
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic
  • reviewed API design and naming
  • reviewed documentation is accurate
  • reviewed tests and test coverage
  • manually tested (if applicable)

}
}
}

return gInfo, result, anteEvents, priority, ctx, err
}

// AggregateEvents aggregation logic of result events (ante and postHander events) with feeEvents
func AggregateEvents(app *BaseApp, resultEvents []abci.Event, feeEvents []abci.Event) []abci.Event {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be helpful to return the error or return some type of success flag. This would make debugging a bit easier to tell when we hit line 755.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather not have any error propagated to the base app for this function and leave that to the implementor of the function. They should determine the correct events to return.

@nullpointer0x00 nullpointer0x00 self-assigned this Sep 30, 2022
@nullpointer0x00 nullpointer0x00 marked this pull request as ready for review September 30, 2022 19:13
@nullpointer0x00 nullpointer0x00 merged commit b08ec4b into release-pio/v0.46.x Sep 30, 2022
egaxhaj pushed a commit that referenced this pull request Dec 2, 2022
…it against cosmos SDK main (cosmos#12478)

## Description

Closes: [#268](osmosis-labs#268)

Adds a Github action that makes it easy to cherry pick commits from a fork PR to main under fork-cherry-pick.yml. The necessity for this PR arises from Mergify / GitHub marketplace currently not having tooling for this kind of action.

How it works:

- Cherry picks the commit of any fork of cosmos-sdk upon a merged PR to main on fork.
- Puts commit into a `pr-patch` branch; makes PR from pr-patch to cosmos:main

---

### Author Checklist

I have...

- [x] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [x] added `!` to the type prefix if API or client breaking change
- [x] targeted the correct branch (see [PR Targeting](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#pr-targeting))
- [x] provided a link to the relevant issue or specification
- [x] followed the guidelines for [building modules](https://github.com/cosmos/cosmos-sdk/blob/main/docs/building-modules)
- [x] included the necessary unit and integration [tests](https://github.com/cosmos/cosmos-sdk/blob/main/CONTRIBUTING.md#testing)
- [x] added a changelog entry to `CHANGELOG.md`
- [-] included comments for [documenting Go code](https://blog.golang.org/godoc)
- [x] updated the relevant documentation or specification
- [x] reviewed "Files changed" and left comments if necessary
- [x] confirmed all CI checks have passed

### Reviewers Checklist

*All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.*

I have...

- [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
- [ ] confirmed `!` in the type prefix if API or client breaking change
- [ ] confirmed all author checklist items have been addressed 
- [ ] reviewed state machine logic
- [ ] reviewed API design and naming
- [ ] reviewed documentation is accurate
- [ ] reviewed tests and test coverage
- [ ] manually tested (if applicable)
@SpicyLemon SpicyLemon deleted the 1092-modify-fee-events-handler branch December 17, 2024 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

3 participants