-
Notifications
You must be signed in to change notification settings - Fork 1
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
Actions and Doctrine to Schema Changes #4
base: main
Are you sure you want to change the base?
Actions and Doctrine to Schema Changes #4
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you a lot, @gangaiamaran for your contribution!
We planned to update this code to support Laravel 11, but you did it! I feel the power of the community! 💪 Great job on this PR. I left some notes for minor changes, please take a look.
Thank you!
@@ -218,4 +210,15 @@ private function formatBytes(int $size, int $precision): string | |||
$suffix = $suffixes[$index]; | |||
return round(1024 ** ($base - floor($base)), $precision).$suffix; | |||
} | |||
protected function getTableSize($connection, string $table) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a final class, there is not a lot of sense in making this method protected. How about making it private? (and adding a return and param types)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -17,4 +24,13 @@ protected function getPackageProviders($app): array | |||
DatabaseToolkitServiceProvider::class, | |||
]; | |||
} | |||
|
|||
protected function tearDown(): void |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea! But I'm not sure we need this in the base TestCase class, because some tests (e.g. unit) may not need DB at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, it's not necessary in the base TestCase class. I'll consider adding it only where needed.
This PR contains the following updates:
Configured MySQL Service in GitHub Actions:
Added Laravel 11 Actions Test Run Support:
Enhanced Test Coverage:
tinyint
) within theFindRiskyDatabaseColumns
command to improve overall test coverage.Next Steps
FindInvalidDatabaseValues
Action URL