We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now if we want to have different fees for different routes we would need to deploy multiple basic/percentage fee handlers.
Introduce _domainResourceIDToFee mapping that will store different fees based on route.
_domainResourceIDToFee
All existing tests are passing after update
The text was updated successfully, but these errors were encountered:
nmlinaric
Successfully merging a pull request may close this issue.
Right now if we want to have different fees for different routes we would need to deploy multiple basic/percentage fee handlers.
Implementation details
Introduce
_domainResourceIDToFee
mapping that will store different fees based on route.Testing details
Acceptance Criteria
All existing tests are passing after update
The text was updated successfully, but these errors were encountered: