Skip to content

trait is missing, commenting trait for temporary update #105

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
wants to merge 1 commit into from

Conversation

awaisali3405
Copy link

No description provided.

@awaisali3405
Copy link
Author

The trait "hasPivotData" is not available in new version of the filament v 3.0

@CodeWithDennis
Copy link
Owner

@saade Can you confirm this or does it simply require a Filament upgrade through composer? (#91 )

@awaisali3405
Copy link
Author

no in filament 3 there no "hasPivotData" trait . So this trait is no longer existing when install this package in my new filament project.

@awaisali3405
Copy link
Author

There is no function related to the hasPivotData trait just remove it i double checked it

@saade
Copy link
Contributor

saade commented Apr 16, 2024

There is, it is available since v3.2.36, just run composer update and you're good to go

@awaisali3405
Copy link
Author

https://github.com/filamentphp/filament/tree/3.x/packages/forms/src/Concerns
i have check all library there is no trait plz recheck

@saade
Copy link
Contributor

saade commented Apr 16, 2024

@awaisali3405 man, HasPivotData was introduced by me in filamentphp/filament#11432. I know what i'm saying.

Here's the file.
https://github.com/filamentphp/filament/blob/3.x/packages/forms/src/Components/Concerns/HasPivotData.php

@saade
Copy link
Contributor

saade commented Apr 16, 2024

You're probably running an old version of Filament. Make sure you're on v3.2.36 or above.

@awaisali3405
Copy link
Author

oh sorry man my mistake for not version in composer lock
Thank for you support.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants