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
First of all, thanks for your hard work on this powerful component system!
I've recently updated Livewire PowerGrid from v6.4.2 to v6.5.2, and unfortunately, the update completely broke my existing setup.
Here are the key details:
In v6.4.2, I had published vendor assets and made several customizations there.
I’m using an Oracle database, so my data comes in as arrays, not Eloquent collections or models.
I had implemented support for these array-based structures using custom logic in the component files.
After updating to v6.5.2, everything stopped working – it seems like many internals were changed, and my overrides or extensions no longer apply.
What I’m requesting:
Better support for array-based/custom collections – especially for users working with non-standard databases like Oracle.
A clear upgrade guide that explains breaking changes, especially for those who previously published and customized vendor files.
If possible, a way to extend or inject custom collection handling without breaking on updates.
Let me know if you'd like me to provide any specific example code or PRs. I’d be happy to help improve support for array-based data if this could be useful for others too.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi PowerGrid team,
First of all, thanks for your hard work on this powerful component system!
I've recently updated Livewire PowerGrid from v6.4.2 to v6.5.2, and unfortunately, the update completely broke my existing setup.
Here are the key details:
In v6.4.2, I had published vendor assets and made several customizations there.
I’m using an Oracle database, so my data comes in as arrays, not Eloquent collections or models.
I had implemented support for these array-based structures using custom logic in the component files.
After updating to v6.5.2, everything stopped working – it seems like many internals were changed, and my overrides or extensions no longer apply.
What I’m requesting:
Better support for array-based/custom collections – especially for users working with non-standard databases like Oracle.
A clear upgrade guide that explains breaking changes, especially for those who previously published and customized vendor files.
If possible, a way to extend or inject custom collection handling without breaking on updates.
Let me know if you'd like me to provide any specific example code or PRs. I’d be happy to help improve support for array-based data if this could be useful for others too.
Thanks again for maintaining this library!
Best regards, Arthur Danielyan
Beta Was this translation helpful? Give feedback.
All reactions