We've identified an issue with the PathSearch function in our React app—it's not delivering the expected results. You can observe the specific error on our page: https://comptox.ai/data.html.
Steps to Address the Issue:
- Determine the Root Cause: We need to ascertain if the glitch is due to rendering issues or if there's a fundamental flaw within the PathSearch function itself.
- Resolve & Test: Once we've pinpointed and rectified the problem, we should be able to utilize the PathSearch function effectively again.
Broader Context & Future Consideration:
The PathSearch function is intrinsically tied to the react-d3-graph package. Given that we're considering replacing react-d3-graph—primarily because it's the root of our package conflicts and it's no longer maintained—it's imperative we have a fully functional PathSearch.
Just a note on the package concerns: Using react-d3-graph currently forces us into using npm install --legacy-peer-deps with React 17. This is not a sustainable practice, as it might lead to problems when updating other packages.
We've identified an issue with the PathSearch function in our React app—it's not delivering the expected results. You can observe the specific error on our page: https://comptox.ai/data.html.
Steps to Address the Issue:
Broader Context & Future Consideration:
The PathSearch function is intrinsically tied to the
react-d3-graphpackage. Given that we're considering replacingreact-d3-graph—primarily because it's the root of our package conflicts and it's no longer maintained—it's imperative we have a fully functional PathSearch.Just a note on the package concerns: Using
react-d3-graphcurrently forces us into usingnpm install --legacy-peer-depswith React 17. This is not a sustainable practice, as it might lead to problems when updating other packages.