Bugfix/eloquent visibility not used

[TheM1984]

Summary

Currently if you would use the HiddenAttributes feature of Eloquent, the enums would still be visible.

This is because they are added after Eloquent hides attributes if needed.

With this change I executed the function to hide the attributes after the AddEnumAttributes was performed.

Test Report

❯ ./vendor/phpunit/phpunit/phpunit
PHPUnit 10.2.7 by Sebastian Bergmann and contributors.

Runtime:       PHP 8.2.8
Configuration: ./enum-eloquent/phpunit.xml

...........................                                       27 / 27 (100%)

Time: 00:00.076, Memory: 14.00 MB

OK (27 tests, 58 assertions)

StyleCI

As far as I can see everything should be good however, I was not able to run the StyleCI test myself.

Edit: saw that the build actions for the PR has a pass for StyleCI

New Functionality Tests

• In case you add new functionality, it must be covered by tests

[fulopattila122]

Nice catch, nice solution, thank you ✌️

I'll merge and release it next week, once I'm back from vacation.

[TheM1984]

Hey, hope you had a good holiday, and the post-vacation workload is not too much.

[TheM1984]

Hey @fulopattila122,

Just a quick note to remind you about this open PR.
If there's anything I can do to facilitate the review process, please feel free to reach out.

Thank you for your time and consideration!
Mark

[fulopattila122]

Thanks for the PR and the pinging; sorry that it took this long

[fulopattila122]

It's not working with Laravel 8: https://github.com/artkonekt/enum-eloquent/actions/runs/6298264476/job/17096781736

I try to fix it, but if it takes too long, I'll just simply drop Laravel 8 support beginning with this release on

[fulopattila122]

I've found the exact minimum version that lets the tests pass, and it is Laravel v8.75.0. I presume that the fix is actually this one: laravel/framework#39880

The respective PR is a test-related fix, so most probably, the code would work outside of the test environment even with Laravel v8.22 - v8.74, but I don't have the bandwidth to prove it, so the next release of this package changes the required minimal Laravel version from 8.22 to 8.75.

Since Laravel 8 is EOL anyway, and upgrading to v8.83 shouldn't be a problem when a project is stuck with Laravel 8, I believe the number of people this change will negatively affect is very close to zero.