Fn svgDrawStraightLinePath and pathfindingAStarNoDiagonal not exported

[davidebibm]

Describe the Bug

Hello, thanks for your effort on this lib!

I'm testing this configurtation but seems that svgDrawStraightLinePath and pathfindingAStarNoDiagonal are not exported.

Minimal Example

https://tisoap.github.io/react-flow-smart-edge/

Steps to Reproduce the Bug or Issue

use the example provided in the doc.

const stepResult = getSmartEdge({
	// ...
	options: {
		drawEdge: svgDrawStraightLinePath,
		generatePath: pathfindingAStarNoDiagonal,
	}
})

Expected behavior

Should work like the example

Screenshots or Videos

export 'pathfindingAStarNoDiagonal' (imported as 'pathfindingAStarNoDiagonal') was not found in '@tisoap/react-flow-smart-edge' (possible exports: SmartBezierEdge, SmartStepEdge, SmartStraightEdge, getSmartEdge, pathfindingAStarDiagonal, svgDrawSmoothLinePath)

Platform

• OS: macOS
• Browser: Chrome
• Version: latest

Additional context

No response

[davidebibm]

#65
Seems to be solved in 4.0.1 but for me is not working

[davidebibm]

@tisoap I've tested it from a local build and it's working... seems that on npm is not distributed the correct dist

If you look at the code on https://www.npmjs.com/package/@tisoap/react-flow-smart-edge?activeTab=code
you will see the missing export in /react-flow-smart-edge/dist/index.d.ts
Could you please check. Thankyou

[jrayappa]

Yep, I have the same issue where the export isn't in the index.d.ts file and can't import pathfindingAStarNoDiagonal

[davidlundmark]

I've run into this issue as well. I really love the straight, non-diagonal edges feature! :)

Is there any timeline for when a fix might be available?

Thanks for all the amazing work on this library!

[nullromo]

I've tested it from a local build

Instructions in case anyone else wants to test this out.

1. Clone this repo
2. npm run build in the repo
3. Copy the repo folder into your node_modules folder, overwriting what was there (node_modules/@tisoap/react-flow-smart-edge).
4. Run your dev server. If you use Vite, you need to use vite --force to clear out Vite's cache.