Mior Muhammad Zaki comments

Results 279 comments of


                                            Mior Muhammad Zaki

Incorrect Signature Generation Due to Channel Name Normalization in PusherBroadcaster.php for private and presence channels.

Hey there, We're closing this issue because it's inactive, already solved, old, or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

[12.x] Fix Eloquent Builder instance in relation class inside closure

Marking as draft since tests are failing.

[12.x] Fix Eloquent Builder instance in relation class inside closure

Hey there, Feel free to submit a new PR with passing tests.

Apostrophe in Maillable::assertSeeInHtml() not escaped properly

Hey there, thanks for reporting this issue. We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code...

Apostrophe in Maillable::assertSeeInHtml() not escaped properly

Hey there, We're closing this issue because it's inactive, already solved, old, or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

jsonSerialize() on relations is not called when serializing the parent model

While it may seem expected, but application may already expect the current behaviour to persist so this is best as a PR to `master` branch.

refactor: Some minor performance & readability enhancements

Marking as draft since tests are failing.

onOneServer() locks are not stored on lock_connection

https://github.com/laravel/framework/blob/e333cc80b8f5414daec8ef7b15c1333685c4988b/src/Illuminate/Foundation/Console/Kernel.php#L312-L314 Laravel uses this value.

Route [] not defined when using filament v3

> Note: when I remove filament v3 it works well. Seems like Filament is currently not compatible with Folio. Have you try creating an issue on the Filament repository?

Route [] not defined when using filament v3

Hey there, We're closing this issue because it's inactive, already solved, old, or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.