Add fix to browser history after navigating to exploration page with no pipeline

[nandhinibsn]

Resolve #

Description:

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

• ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
• PRE-COMMIT. You ran pre-commit on all commits, or else, you
  ran pre-commit run --all-files at the end.
• USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
  our users.
• DEV CHANGES.
  • Update the documentation if this PR changes how to develop/launch on the app.
  • Update the README files and our wiki for any big design decisions, if relevant.
  • Add unit tests, docstrings, typing and comments for complex sections.

[nandhinibsn]

There was a console error which occurred when we navigate to the exploration page with no pipeline.

I simplified the solution to navigating on the Dashboard page instead of the Exploration page. I believe it's more of a simplified way. Let me know your thoughts @JosephMarinier

[nandhinibsn]

Hey @JosephMarinier, the solution added to Dashboard has been reverted as it resolved the issue with tracking history. Still, it did not switch tabs from prediction overview to utterance table if no pipeline was selected from the exploration page.

Additionally, I understood why the console error was caused by reading this blog.

To solve the bug, I added useEffect to handle the pipeline change from the exploration page to solve the issue with tracking history while the console error is not occurring anymore. Let me know what you think

[JosephMarinier]

Excellent! 👍
As you said, the React.useEffect is perfect for if you select No pipeline when already on the Exploration Space. However, when navigating from the Dashboard to the Exploration Space, it now works (👍) but it adds an intermediary state in the history, on the invalid Prediction Overview tab. So, I think the two solutions could be combined. You could also add your initial solution to the Link to= on the Dashboard, to polish the navigation. It also has the advantage of showing the correct destination when hovering the button.

[nandhinibsn]

Excellent! 👍 As you said, the React.useEffect is perfect for if you select No pipeline when already on the Exploration Space. However, when navigating from the Dashboard to the Exploration Space, it now works (👍) but it adds an intermediary state in the history, on the invalid Prediction Overview tab. So, I think the two solutions could be combined. You could also add your initial solution to the Link to= on the Dashboard, to polish the navigation. It also has the advantage of showing the correct destination when hovering the button.

Okay, Make sense. I will add the condition back to the Dashboard page.

[JosephMarinier]

🚢 🇮🇹

[nandhinibsn]

Thank you for your time and valuable suggestion :)