Skip to content

Conversation

ukane-philemon
Copy link
Collaborator

This commit fixes a bug where the int value of treasury tx types was used to construct page links instead of its string value. As a result, page navigation on the treasury page did not function correctly because the string value is expected to return correct table values.

Others:

  • Replace duplicated code used in parsing URL params in *explorerUI.TreasuryPage with improved parseTreasuryParams helper function.
  • Remove unused code from when AddressPage was used to display treasury data.
  • Remove resolved TODO and refactor how treasury mempool data is passed to the HTML template.


Closes #2018

This commit fixes a bug where the int value of treasury tx types was used
to construct page links instead of its string value. As a result, page navigation
on the treasury page did not function correctly because the string value is expected
to return correct table values.

Others:
- Replace duplicated code used in parsing URL params in *explorerUI.TreasuryPage with
  improved parseTreasuryParams helper function.
- Remove unused code from when *explorerUI.AddressPage was used to display treasury data.
- Remove resolved TODO and refactor how treasury mempool data is passed to the HTML template.


Signed-off-by: Philemon Ukane <[email protected]>
Signed-off-by: Philemon Ukane <[email protected]>
parsePaginationParams is used for both address and treasury page.
Both pages have different values as defaults.

This commit ensures the correct default is used for each caller.

Signed-off-by: Philemon Ukane <[email protected]>
@ukane-philemon
Copy link
Collaborator Author

#2018 (comment) is fixed in 2b6c76b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: page navigation on treasury page does not function correctly

1 participant