Ambiguity with the other laravel-async

[Vectorial1024]

There is another library also called laravel-async https://github.com/vuongxuongminh/laravel-async/tree/main

This may cause confusion; is this related to that laravel-async or is this something different? A different package name might be needed.

[saeedvaziry]

First time seeing that package, but looks like it is a way to run code in parallel and the main process should be still running until the child process finishes.

My package is built to send the whole process into the background (no parent child) and just return the HTTP response to the client.

[Vectorial1024]

Good to hear that; at least this library is not some unintended fork of some other library.

Just to make sure we are on the same page, having 2 libraries with the same name + basically the same goals can confuse people (e.g. me) by unintentionally implying a repo fork relationship. Usually when people fork something, they keep the same package name. Seeing this side is newer (first commit late 2023) than the other side (first commit mid 2019), people might accidentally think this side is a fork of the other side.

Seeing how popular this library can become (again, I genuinely think this library can be a real gamechanger), either you are made aware of this coincidence (hence this issue) and be ready to face the potential spiciness in the future, or you rename this package asap and avoid dealing with the future spiciness.