Jonathan Cornaz

> Can you use the --extends parameter? You can pass it a filepath 😄 Can you show a complete example? Sorry but it isn't clear to me. I looked at...

>The docs say: > >> List of modules or file paths > > It can be a simple module (i.e. a js file), if you give it a full path....

> I just tried this with semantic-release --extends ./.config/semantic-release.json and it worked. Would it work if the config was a `yaml` file? > This might be worth mentioning in the...

Yes, definitely. It is not yet exactly clear how it will look like though. Right now, I would lean toward simply adding a "ray" shape that could be created like...

> I wonder if it should be on CollisionShape, or a separate component entirely I wonder too. Though, being a collision shape makes it very simple. I am not really...

Maybe something like: ```rust let shape = CollisionShape::new_circle(1.0); let ray_origin = Vec2::new(-2.0, 0.0); let ray = Vec2::X * 2.0; assert!(shape.collides_with_ray(Ray::new(ray_origin, ray)); ``` Or using a ray shape: ```rust let shape...

Well, because it is a `CollisionShape` doesn't mean it needs to be used as a component when using bevy. It can still be created on the fly the same way....

Thanks for sharing :-) I'll probably go a different route though, I'll try to follow up on the GJK/EPA algorithms already in place and using properties of the Minkowski difference....

By the way, can you tell me more about your use case? What is your use of ray cast currently?

> My use for ray casting is to create a 2D player controller (without a physics engine) by casting rays from the player on all sides and checking it with...