Change Details

This revision is to fix a bug where we render a nested anchor tag in our <TxHistory /> component. Also added some types to map our behavior and wrote some tests for <TxHistory />. My strategy to fix the bug was: replacing the surrounding the parent `<a>` tag with a styled `<span>` tag. (the styling replicates the styling of an `<a>` tag). adding a `role="link"` to said span tag, to make it aware to screen readers that this is a span element with "link" functionality.

This revision is to fix a bug where we render a nested anchor tag in our <TxHistory /> component. Also added some types to map our behavior and wrote some tests for <TxHistory />. My strategy to fix the bug was: replacing the surrounding the parent `<a>` tag with a styled `<span>` tag. (the styling replicates the styling of an `<a>` tag). adding a `role="link"` to said span tag, to make it aware to screen readers that this is a span element with "link" functionality. ----- I also added some tests and propTypes. Since I am new to the project, I mapped out the types for transactions and I decided to update the PropTypes (for my benefit, and others) from my discovery reading through the code base. My analysis of the types might be wrong so please correct me!

This revision is to fix a bug where we render a nested anchor tag in our <TxHistory /> component. Also added some types to map our behavior and wrote some tests for <TxHistory />. My strategy to fix the bug was: replacing the surrounding the parent `<a>` tag with a styled `<span>` tag. (the styling replicates the styling of an `<a>` tag). adding a `role="link"` to said span tag, to make it aware to screen readers that this is a span element with "link" functionality. ----- I also added some tests and propTypes. Since I am new to the project, I mapped out the types for transactions and I decided to update the PropTypes (for my benefit, and others) from my discovery reading through the code base. My analysis of the types might be wrong so please correct me!