-
Notifications
You must be signed in to change notification settings - Fork 2
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 the app to use Symfony 6 and PHP 8.2 #178
Upgrade the app to use Symfony 6 and PHP 8.2 #178
Conversation
Before upgrading to SF6 and upgrading all dependencies, I opted to first upgrade the qa tooling. They will not pass by any means at this point.
We now use our own docker based devconf
If we want code coverage stats, we can use scrutenizer for that purpose
The legacy folder was renamed to openconext (as decided to be the way forward) The .env files only contained env overrides and allowed for setting the secret
That more closesly matches the modern symfony ways The webpack setup needed some small tweaking in order to keep things in a functioning state
This should have resulted in 500 errors in the tiqr app previously.
Level 8 and 9 have mostly been ignored as most of the warnings where hailing from the behat contexts
e96cafb
to
03f96f7
Compare
We have a test folder, but there are no tests. The folder is kept, and PHP Unit is standing by for future development where we might want to utilize PHP unit testing
7c1ec80
to
771aa69
Compare
a8f3202
to
cc17ef9
Compare
composer.json
Outdated
}, | ||
"scripts": { | ||
"test": [ | ||
"check": [ | ||
"@composer-validate", |
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 also ran in ci/qa/validate , is this because it needs to get validated from both inside and outside composer.json ?
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 found a bug here!
I now call the validate script which for now performs the same logic, but it could just as well do more than just validate the composer lockfile.
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.
Wow what a changes... certainly a big step into cleaner code!
Also optimized imports with it.
Thanks for the many good suggestions @parijke I did not fix all of them. Most of the dev/test related stuff is left as-is. As they add limited added value for now. If you disagree, feel free discuss. |
db638c1
to
3944dcf
Compare
The form was not using the correct bootstrap form classes so was ugly
35ddce5
into
feature/build-and-publish-test-container
This marks the end of an era. The code has been:
App/
namespace. Tiqr now also adheres to the Vendor/Projectname convetion. And was baptized:Surfnet/Tiqr
On other fronts: