Hash navigation is colliding with the existing hash navigation

Using ReDoc as not a stand alone application, but a part of a framework that's an SPA.
I am using ant.design, a react application as a boiler plate. I want to integrate ReDoc on one of its tab.
I already have a route provider in the application (ex: localhost:8000/#/dashboard/workspace). now while I am trying to use ReDoc component RedocStandalone, while navigating, it already uses this # string, which is causing problem while navigation.

I want something, so that I could access the ReDoc app such after my URL - localhost:8000/#/dashboard/workspace/#section/Authentication, where I need to replace second # with encoded # to navigate smoothly!

Or is there any other way of implementing this, I am unaware of? Please help.

@RomanGotsiy

Start by reproducing the hash collision when RedocStandalone is mounted inside the existing SPA route, using the example URL and the section/Authentication navigation described in the issue. Trace how the host route and ReDoc section navigation consume the hash, then verify that both the application's route and ReDoc's section navigation work without conflicting URL fragments.