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

Symfony 6.4 upgrade #620

Merged
merged 135 commits into from
Feb 15, 2024
Merged

Symfony 6.4 upgrade #620

merged 135 commits into from
Feb 15, 2024

Conversation

parijke
Copy link
Contributor

@parijke parijke commented Jan 16, 2024

Upgraded to php 8.2 and symfony 6.4
Added phpstan

@parijke parijke marked this pull request as ready for review January 25, 2024 09:49
@parijke parijke requested a review from MKodde January 25, 2024 09:49
Copy link
Contributor

@MKodde MKodde left a comment

Choose a reason for hiding this comment

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

Recurring issues:

  1. I noticed a lot of commented strict_type declarations. Why did you disable them? If we are not adding strict types there, please remove them. But even better, I much prefer we enable strict typing throughout the app.
  2. A lot of PHPDoc type hints are still present. Please remove them and at those points I missed type definitions.
  3. The removal of the if (empty($foobar)) condition that you replaced with the !=='' || == '0' || .. construction does not sit right with me. I'd like to see the original to return. Or that you implement an alternative that is not so expressive.

@quartje quartje force-pushed the feature/symfony6-upgrade branch 2 times, most recently from 36ecc86 to 3c04dcb Compare January 29, 2024 14:44
Copy link
Contributor

@MKodde MKodde left a comment

Choose a reason for hiding this comment

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

  1. The Test integration run is not green yet. Hangs on a lockfile issue as it seems
  2. I'd still like to discuss the introduction of this logic. The code maybe became more type safe that way, but readability took a big hit here IMHO.
$entity->getId() === null || $entity->getId() === '' || $entity->getId() === '0';

Perhaps we can move this check to a helper function, reinstate the old behavior, ... insert your ideas here ...

ci/qa/phpcs.xml Outdated Show resolved Hide resolved
@parijke parijke force-pushed the feature/symfony6-upgrade branch from fe57b7c to 67c979c Compare February 7, 2024 15:16
@parijke
Copy link
Contributor Author

parijke commented Feb 8, 2024

I think all rleft over review points are addressed now

@parijke parijke requested a review from MKodde February 8, 2024 08:25
@MKodde MKodde changed the title Feature/symfony6 upgrade Symfony 6.4 upgrade Feb 14, 2024
Copy link
Contributor

@MKodde MKodde left a comment

Choose a reason for hiding this comment

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

Ship it, my Spanish friend. Would you be so kind to:

  • First rebase the recent Jira changes?
  • Update the PR description
  • Update the Wiki checklist
  • Review the git history of this PR, you can decide to leave the log, or to squash merge them into 1. I think the log is good'enuff to merge it as is. But your the judge in the end.
  • Create a new release branch for this release (and update the changelog.md accordingly)
  • Tag it

@parijke parijke force-pushed the feature/symfony6-upgrade branch from de724aa to 5844d59 Compare February 15, 2024 09:23
@parijke parijke force-pushed the feature/symfony6-upgrade branch from 5844d59 to 44be7d5 Compare February 15, 2024 09:32
@parijke parijke merged commit e0ed64e into main Feb 15, 2024
2 checks passed
@MKodde MKodde deleted the feature/symfony6-upgrade branch June 12, 2024 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants