Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Laravel 11 #10972

Merged
merged 42 commits into from
Feb 27, 2024
Merged

Laravel 11 #10972

merged 42 commits into from
Feb 27, 2024

Conversation

danharrin
Copy link
Member

@danharrin danharrin commented Jan 21, 2024

@danharrin danharrin added this to the v3 milestone Jan 21, 2024
@danharrin danharrin marked this pull request as draft January 21, 2024 15:04
@tisuchi
Copy link

tisuchi commented Feb 10, 2024

Hi @danharrin

Thanks for the nice work.

Does it mean that we need to Laravel 11 to merge this pull request?

If we want to install filament with laravel 11-dev, is there any way to do that?

@danharrin
Copy link
Member Author

If you would like to use it, you can contribute to eloquent-serialize and power-joins with Laravel 11 support. Once those packages have support, we can merge this PR.

@atmonshi
Copy link
Contributor

is there any knowing issues with eloquent-serialize and L11?
aside from adding |^11.0?
test it with fresh installation L11 seems all fine.

$package = EloquentSerializeFacade::serialize(
        \App\Models\User::query()
            ->limit(2)
    );

    dump($package);
    
    $builder = EloquentSerializeFacade::unserialize($package);
    foreach ($builder->get() as $item) {
        dump($item);
    }

@danharrin
Copy link
Member Author

I can't imagine there will be issues, just needs to be a PR

@staudenmeir
Copy link

https://github.com/staudenmeir/belongs-to-through
https://github.com/staudenmeir/eloquent-has-many-deep

Both packages now have versions for Laravel 11. The constraints in your composer.json don't need to be changed.

@danharrin
Copy link
Member Author

Thanks @staudenmeir, will watch out for the tags

@danharrin
Copy link
Member Author

I'm still unable to run CI because of spatie/eloquent-sortable which is required by spatie/laravel-tags @mokhosh

@mokhosh
Copy link
Contributor

mokhosh commented Feb 25, 2024

I'm still unable to run CI because of spatie/eloquent-sortable which is required by spatie/laravel-tags @mokhosh

on it @danharrin spatie/eloquent-sortable#171

@mokhosh
Copy link
Contributor

mokhosh commented Feb 26, 2024

spatie/eloquent-sortable#171 done @danharrin

@mokhosh
Copy link
Contributor

mokhosh commented Feb 26, 2024

https://github.com/spatie/eloquent-sortable/releases/tag/4.2.0 tagged 🎉

👀

@mokhosh
Copy link
Contributor

mokhosh commented Feb 26, 2024

The failed tests seem to be related to LazilyRefreshDatabase but there are only two v10 changes to this trait. I didn't see any changes to it on master.
These are the changes:
laravel/framework#49853
laravel/framework#49914

It could also be https://github.com/laravel/framework/commits/master/src/Illuminate/Foundation/Testing/RefreshDatabase.php

@danharrin
Copy link
Member Author

The first error is about a table not existing, maybe the rest of the errors are caught up because of that. Seems like maybe our migrations don't get picked up

@danharrin
Copy link
Member Author

danharrin commented Feb 26, 2024

Seems to be a similar issue here, but it might be Passport related spatie/laravel-permission#2605

@mokhosh
Copy link
Contributor

mokhosh commented Feb 26, 2024

im on mobile, and github is clunky on mobile, but i would check how laravel/passport has adapted its tests on master to support laravel11

@danharrin
Copy link
Member Author

The PR I sent has not had the issue solved

@mokhosh
Copy link
Contributor

mokhosh commented Feb 27, 2024

I went through laravel/framework PRs and commits, but now I'm thinking it's a testbench issue. I created an issue here: orchestral/testbench#393

@danharrin
Copy link
Member Author

Thanks to @crynobone, the tests are now passing!

@danharrin danharrin merged commit 303ef3c into 3.x Feb 27, 2024
21 checks passed
@danharrin danharrin deleted the laravel-11 branch February 27, 2024 15:30
@mokhosh
Copy link
Contributor

mokhosh commented Feb 27, 2024

Awesome, thanks @crynobone and @danharrin

@AJenbo
Copy link

AJenbo commented Feb 29, 2024

Glad to see you managed to solve it 👍

@marcelloinfoweb
Copy link

Any news about this?

@mokhosh
Copy link
Contributor

mokhosh commented Mar 14, 2024

@marcelloinfoweb about what man?

@marcelloinfoweb
Copy link

@marcelloinfoweb about what man?

If Filament is already supported in Laravel 11

@mokhosh
Copy link
Contributor

mokhosh commented Mar 14, 2024

It sure is @marcelloinfoweb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

9 participants