PHP8.1 compatibility

[eboye]

Description

I've bumped the php version to 8.1 and added some strict types

Motivation and context

Future versions compatibility

How has this been tested?

unit tests included in the project

Screenshots (if appropriate)

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have read the CONTRIBUTING document.
• My pull request addresses exactly one patch/feature.
• I have created a branch for this patch/feature.
• Each individual commit in the pull request is meaningful.
• I have added tests to cover my changes.
• If my change requires a change to the documentation, I have updated it accordingly.

[yusufkandemir]

Looking great 👏 I requested some changes to improve clarity.

[eboye]

Sure, no specific reasons why I used those, just a matter of habit adding those :)

[yusufkandemir]

@eboye did you forget to push your changes, or will you push them later? 🙂

[eboye]

Sorry, here they are.

The only thing I want to mention is that this one test fails after my tinkering:

TypeError : PHPUnit\Framework\Assert::assertContains(): Argument #2 ($haystack) must be of type iterable, string given, called in ~/GitHub/microdata-parser/tests/MicrodataParserTest.php on line 82
~/GitHub/microdata-parser/tests/MicrodataParserTest.php:82

[yusufkandemir]

@eboye thanks for the contributions! I made more changes, migrated to Pest from PHPUnit, migrated to GitHub actions from all other CI tools, and improved the code quality, then released https://github.com/yusufkandemir/microdata-parser/releases/tag/v1.0.0, enjoy!

[eboye]

Great!