-
Notifications
You must be signed in to change notification settings - Fork 7
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
Some style and general improvements #8
base: Main
Are you sure you want to change the base?
Conversation
…k from the project
Without https the link to the blog doesn't work.
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.
Hey @kudashevs - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟡 General issues: 1 issue found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Docstrings: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.
@@ -67,7 +67,7 @@ Examples | |||
--- | |||
ApprovalTests eats it own dogfood, so the best examples are in the source code itself. | |||
|
|||
None the less, Here's a quick look at some | |||
None the less, here's a quick look at some |
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.
nitpick (typo): Fixing the typo in 'None the less' improves the document's professionalism.
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'd better ask the author of the text, not me, why they've used this interesting verbiage.
And this is actually the archaic way of spelling "nonetheless", so why not?
Hello,
It wasn't possible to make this PR small, sorry. It fixes a lot of formatting issues; that's why it might seem bloated, but it really isn't.
So, I would like to propose some style and general improvements to the project. For your convenience, I'm going to list them in the same order as the
Files changed
tab shows:.editorconfig
PHP files wildcard pattern and apply the rules to all the PHP files (mostly a new line at the end of a file).editoconfig
rules to other files (including.yml
and.json
files)build.yml
workflow switch toubuntu-latest
build.yml
workflow add support for new PHP (8.2, 8.3) and PHPUnit (10, 11) versions.gitignore
add new exclusions (includingcomposer.lock
- explanation in the next improvement)composer.lock
file from the project (it is not recommended to store it in the repo for libraries)composer require
is more common)https://
prefix)composer.json
move the Tests namespace to the development environmentcomposer.json
add a scripts section (it allows running tests through the composer, very convenient)If this PR is too big, I can try to divide it into three smaller ones. @isidore let me please know, if you need any help with this PR.