Fixed: the routing from the query page to the route list page

[ymaheshwari1]

Related Issues

Closes #62

Short Description and Why It's Useful

Removed usage of ion-chip and replaced with ion-back-button to make the navigation work as expected and we don't need to handle the navigation from route details to the run details page using push that results in breaking the navigation from run details to runs page.

Screenshots of Visual Changes before/after (If There Are Any)

After:

When using color="medium" on ion-back-button (Not added in the code just added the screenshot)

Contribution and Currently Important Rules Acceptance

• I read and followed contribution rules

[dt2patel]

Are we required to use ion back button if we want to manage routing correctly? I feel like we should be allowed to add a corresponding pop/back action to any element we want right?

[ymaheshwari1]

Are we required to use ion back button if we want to manage routing correctly? I feel like we should be allowed to add a corresponding pop/back action to any element we want right?

We have method to go to specific page using router.go(number) in the route history, but as we have support to move to the settings page from the query page, if the user moves to the settings page a new route entry gets added in the history and when clicking back from query page, the user gets redirected to the settings page, as user is coming from the settings page.

The above method depends on the position of the route relative to the currentRoute.