Chimit

It would also be nice to support the case when the "from" field is translatable, but `slug` is not and uses one of the languages.

@freekmurze any plans to support it?

I think comma separated values is a popular case enough to make a special validation rule.

In APIs it's a common situation when CSV are used instead of arrays: ``` GET /groups?type=public,private ``` and ``` GET /groups?type[0]=public&type[1]=private ```

I use a custom middleware to turn comma-separated values into arrays and validate them as arrays. ```php namespace App\Http\Middleware; use Closure; class CsvToArray { /** * Handle the incoming request....

I found only one way to simulate these values by using raw objects: ```php /** * IncomingMessage constructor * * @param string $message * @param string $sender * @param string...

[1.4.0](https://github.com/beyondcode/laravel-favicon/releases/tag/1.4.0) doesn't work with the latest Laravel as well. ``` Problem 1 - Root composer.json requires beyondcode/laravel-favicon ^1.4 -> satisfiable by beyondcode/laravel-favicon[1.4.0]. - beyondcode/laravel-favicon 1.4.0 requires illuminate/http 5.6.*|5.7.*|5.8.*|6.*|7.*|8.* -> found...

I tried to send voip push notifications, but apparently this package doesn't automatically add a `.voip` suffix to the bundle id. > voip > ... > If you set this...

Apparently, we can close this issue along with this one https://github.com/edamov/pushok/issues/97

The problem is still there and is thrown randomly on the line 154. I can see it in logs. https://github.com/botman/driver-telegram/blob/b681bf94a8e1537c385a34131e8de8075c3866c8/src/TelegramDriver.php#L154 I can reliably reproduce it when I'm trying to delete...