Skip to content

v5.0 - Symfony 7 support and refactoring #57

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

Merged
merged 2 commits into from
Jun 21, 2024
Merged

Conversation

michnovka
Copy link
Contributor

Cleanup of old unused code. Bumped dependencies. Strict type all.

@michnovka
Copy link
Contributor Author

michnovka commented Jun 19, 2024

Closes #54 and #56, supersedes #55

Copy link
Contributor Author

@michnovka michnovka left a comment

Choose a reason for hiding this comment

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

I have just one comment to be addressed, please have a look @mac-cain13

@@ -212,22 +213,6 @@ private function getMemoryInfo(bool $peak = false): array
return $info;
}

/**
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mac-cain13 I could not find any reason whatsoever to override the setCode function in our class. We call parent::setCode inside constructor. the code we execute is programmed in the derived classes inside its functions, which are called from the runloop. So why setCode is important? Also the function was copy of the parent function from Symfony 2, since Symfony 3 different code was used using Closure class. Yet another example why I think his was never used, thus the inconsistency never manifested as a bug.

@mac-cain13 mac-cain13 merged commit 41ca1df into mac-cain13:master Jun 21, 2024
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.

2 participants