`Path` is not available about bevy_prototype_lyon

[rparrett]

I tidied up and pushed my local fork that backports some of the features added since 0.3.1 to bevy 0.5 in case this is useful to you. It may not be doing exactly what you need with paths, but it could be a head start.

https://github.com/rparrett/bevy_prototype_lyon/tree/features-for-bevy-0.5

[Nilirad]

You can access it through bevy_prototype_lyon::prelude::tess::path::Path.

However, in most cases you can simply use ShapePath to generate a Path component from a Geometry.

[ManevilleF]

There is no tess module in bevy_prototype_lyon::prelude and I don't see any struct ShapePath anywhere.

I need to use Path in a component query to be able to dynamically edit my shape

[ManevilleF]

You can access it through bevy_prototype_lyon::prelude::tess::path::Path.

However, in most cases you can simply use ShapePath to generate a Path component from a Geometry.

It seems that I have to use your main branch to access these features and not the released version. It means I have to use the bevy main branch as well.

Why is the master branch up to date with bevy main? You should have a tracking branch and MR instead

[ManevilleF]

Thanks !

[Nilirad]

Why is the master branch up to date with bevy main? You should have a tracking branch and MR instead

I track Bevy main on the master branch because I want to develop based off the latest changes on Bevy, like it would if it was just one of the Bevy crates. Then, when I want to release, I just branch out from master, change the Bevy dependency to the latest release and eventually fix any breaking change added by Bevy main after release (this last step is rare though, since I tend to release shortly after Bevy).

I used to have a tracking branch but I didn't like the unnecessary complexity of that approach.

Closing this as the problem has been resolved.