You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When upgrading to latest version (3.4.17) there's console bug Livewire property [tableName] cannot be found from this PR and i think from this line.
defining property to table component like public string $tableName = 'some-table'; fix the bug. but is it really required to define $tableName from version 3.4.17?
Here's the console error looks like:
How to reproduce the bug
No response
Package Version
3.4.17
PHP Version
None
Laravel Version
No response
Alpine Version
No response
Theme
None
Notes
No response
Error Message
No response
The text was updated successfully, but these errors were encountered:
It shouldn't be required as there's a method used to retrieve the default "table" if it's not defined, I'll take a look, it's probably just a mistaken entangle rather than a get, or the default property is mistyped as protected/private
What happened?
When upgrading to latest version (3.4.17) there's console bug
Livewire property [tableName] cannot be found
from this PR and i think from this line.defining property to table component like
public string $tableName = 'some-table';
fix the bug. but is it really required to define$tableName
from version3.4.17
?Here's the console error looks like:
How to reproduce the bug
No response
Package Version
3.4.17
PHP Version
None
Laravel Version
No response
Alpine Version
No response
Theme
None
Notes
No response
Error Message
No response
The text was updated successfully, but these errors were encountered: