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

Upgrade to Symfony v5.4 minimum #265

Closed
wants to merge 9 commits into from
Closed

Conversation

94noni
Copy link
Contributor

@94noni 94noni commented Jun 16, 2023

Pull Request

Related issue

Fixes #263 (Symfony part)

What does this PR do?

@94noni 94noni changed the title [WIP] Upgrade to Symfony v5.4 minimum Upgrade to Symfony v5.4 minimum Jun 20, 2023
@94noni
Copy link
Contributor Author

94noni commented Jun 20, 2023

@norkunas should rector be kept (for later usage?)
PR is ready nonetheless

@94noni 94noni requested a review from norkunas June 20, 2023 15:57
@norkunas
Copy link
Collaborator

@norkunas should rector be kept (for later usage?)

@brunoocasali should decide, but in case we need it very rarely if at all, maybe we shouldn't introduce as dev dependency to save some resources

@norkunas
Copy link
Collaborator

By the way Symfony 6.3 should be added to matrix

@94noni
Copy link
Contributor Author

94noni commented Jun 21, 2023

Oki will do indeed the new 6.3
And remove rector for now as project is small so lets keep it simple

@94noni 94noni changed the title Upgrade to Symfony v5.4 minimum [WIP] Upgrade to Symfony v5.4 minimum Jun 21, 2023
@brunoocasali
Copy link
Member

@brunoocasali should decide, but in case we need it very rarely if at all, maybe we shouldn't introduce as dev dependency to save some resources

I'm not opposed to keeping it, but my go-to opinion about this is: not to add new dependencies, even dev ones. So if we can remove it let's do it! :)

@94noni 94noni changed the title [WIP] Upgrade to Symfony v5.4 minimum Upgrade to Symfony v5.4 minimum Jun 25, 2023
@94noni
Copy link
Contributor Author

94noni commented Jun 25, 2023

@brunoocasali @norkunas friendly ping, PR ready for reviews :)
cheers

@norkunas
Copy link
Collaborator

@brunoocasali @norkunas friendly ping, PR ready for reviews :) cheers

lgtm

@brunoocasali brunoocasali added the breaking-change The related changes are breaking for the users label Jul 3, 2023
brunoocasali
brunoocasali previously approved these changes Jul 3, 2023
Copy link
Member

@brunoocasali brunoocasali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bors merge

@brunoocasali
Copy link
Member

Can you check the CI error @94noni? 😇

@94noni
Copy link
Contributor Author

94noni commented Jul 5, 2023

i will have a look at it indeed, hopefully soon :)

norkunas
norkunas previously approved these changes Jul 10, 2023
@brunoocasali
Copy link
Member

Hi @94noni, it is because you never got a PR merged. As soon you merge your first one, the CI will automatically run :) it is just a way to avoid spam (I think so)!

@norkunas
Copy link
Collaborator

norkunas commented Jul 11, 2023

6.1.* fails, I suggest to leave overriding public static function getDefaultName() and public static function getDefaultDescription() so they will work on all versions

@94noni
Copy link
Contributor Author

94noni commented Jul 11, 2023

indeed, with the swap to attribute, but the bundle is not sf6+ so we will need to add those back yes
I will update this PR shortly, hopefully CI will be ok :)

@norkunas
Copy link
Collaborator

can you try git commit --amend --no-edit && git push -f to retrigger CI? not sure why integration-tests (PHP 8.2) (Symfony 6.2.*) does not run

@brunoocasali
Copy link
Member

bors try

@norkunas
Copy link
Collaborator

We should merge #266 before

@brunoocasali
Copy link
Member

Yeah, I was trying to force this CI action to trigger but had no success, either! Let's fix the conflicts then after approved we can see what is happen.

@94noni
Copy link
Contributor Author

94noni commented Jul 29, 2023

as #266 will hopefully be merged shortly, I will rework on this right after
thx

meili-bors bot added a commit that referenced this pull request Aug 3, 2023
266: Use meilisearch prefix for services r=brunoocasali a=94noni

# Pull Request

## What does this PR do?
- Improves "best practices/coding standard" as the « search » prefix is to generic, lets be specific for this bundle

This PR can be merged before #265 (as it will require a major release)

TODO:
Assert that the container has all services and that deprecations are triggered 

- https://symfony.com/doc/5.4/bundles/best_practices.html#services
- https://symfony.com/doc/5.4/service_container/alias_private.html#deprecating-service-aliases



---------

# RFC

I found some inconsistency reading the repo:

- Commands namespace: `meili:`
- Bundle config: `meili_search`
- Services: `search` (this PR)

Will it be nice to define them as `meilisearch`everywhere? 


Co-authored-by: Antoine Makdessi <[email protected]>
@brunoocasali
Copy link
Member

I just merged the #266 @94noni thanks a lot for your help :)

@94noni
Copy link
Contributor Author

94noni commented Aug 3, 2023

@brunoocasali seems a failure in the merge, will wait a little bit to restart this
also needed for #275

thx !

meili-bors bot added a commit that referenced this pull request Aug 3, 2023
266: Use meilisearch prefix for services r=brunoocasali a=94noni

# Pull Request

## What does this PR do?
- Improves "best practices/coding standard" as the « search » prefix is to generic, lets be specific for this bundle

This PR can be merged before #265 (as it will require a major release)

TODO:
Assert that the container has all services and that deprecations are triggered 

- https://symfony.com/doc/5.4/bundles/best_practices.html#services
- https://symfony.com/doc/5.4/service_container/alias_private.html#deprecating-service-aliases



---------

# RFC

I found some inconsistency reading the repo:

- Commands namespace: `meili:`
- Bundle config: `meili_search`
- Services: `search` (this PR)

Will it be nice to define them as `meilisearch`everywhere? 


Co-authored-by: Antoine Makdessi <[email protected]>
meili-bors bot added a commit that referenced this pull request Aug 8, 2023
266: Use meilisearch prefix for services r=norkunas a=94noni

# Pull Request

## What does this PR do?
- Improves "best practices/coding standard" as the « search » prefix is to generic, lets be specific for this bundle

This PR can be merged before #265 (as it will require a major release)

TODO:
Assert that the container has all services and that deprecations are triggered 

- https://symfony.com/doc/5.4/bundles/best_practices.html#services
- https://symfony.com/doc/5.4/service_container/alias_private.html#deprecating-service-aliases



---------

# RFC

I found some inconsistency reading the repo:

- Commands namespace: `meili:`
- Bundle config: `meili_search`
- Services: `search` (this PR)

Will it be nice to define them as `meilisearch`everywhere? 


Co-authored-by: Antoine Makdessi <[email protected]>
Co-authored-by: Tomas Norkūnas <[email protected]>
@brunoocasali
Copy link
Member

bors merge

@curquiza
Copy link
Member

Hello @94noni can you rebase your branch please? 😊
There are git conflicts so we cannot merge

@94noni
Copy link
Contributor Author

94noni commented Sep 13, 2023

@curquiza thx for the ping, I've tried resolving on GitHub.com ui, hope it is good
i will not have time available to finish soon this PR and thus also the following one #275

@norkunas please feel free to continue and proceed with PRs

Comment on lines +14 to 25
protected static $defaultName = 'meilisearch:clear|meili:clear';
protected static $defaultDescription = 'Clear the index documents';

public static function getDefaultName(): string
{
return 'meilisearch:clear|meili:clear';
return self::$defaultName;
}

public static function getDefaultDescription(): string
{
return 'Clear the index documents';
return self::$defaultDescription;
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Revert this, as there is no point to do this at current time. When we'll be able to provide info via attributes we will.
Same in other commands

@Chris53897
Copy link
Contributor

@94noni Thanks for your work. Do you have some time to finish this PR? After that PR is merged, Symfony 7 support will be easier to implement.

@94noni
Copy link
Contributor Author

94noni commented Nov 1, 2023

@Chris53897 not so much sadly at the moment
If anyone wants to take over and finish it i will be more than happy to review etc

@Chris53897 Chris53897 mentioned this pull request Nov 3, 2023
2 tasks
@94noni
Copy link
Contributor Author

94noni commented Nov 9, 2023

closing in favor of #301 which takes over
thanks for original reviewers and @Chris53897 for continuing :)

@94noni 94noni closed this Nov 9, 2023
@94noni 94noni deleted the issue-263 branch November 9, 2023 18:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change The related changes are breaking for the users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[RFC] bump php to v8+ and Symfony to v5.4+
5 participants