feat: add support for different fees per dest domain to basic/percentage fee handler #206
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.
Description
This introduces a mapping for fees per destination domain. Now we don't have to deploy a new handler for every fee amount, they all can be setup in a single basic/percentage fee handler.
Also removes setting up fees in migrations since now there would be too many moving parts to do it automatically.
In general we need to rethink about fees and how to approach to migrations.
Related Issue Or Context
Closes: #205
Closes: #151
How Has This Been Tested? Testing details.
existing unit and e2e tests are updated
Types of changes
Checklist: