Doc comments + GET query params

[Menkveld-24]

Hi.
I had this bit of code for my own project and was wondering what might be of use to merge into your main repository.
I added so that if you have a request scheme for a get request that it'd show up as query parameters instead of at the body.
I also added that comments above the functions/route handlers in controllers we're added as 'documentation' to the postman route (useful for sharing the api documentation internally with colleagues e.g.).
Haven't written any tests for this. I'll refine this along with tests if you think any of these 2 features is useful.

Kind regards,
Menke

The query params on a get request.

The documentation (comment above the function)

[andreaselia]

This is an interesting idea, thanks for sharing it with us and everyone else who uses the package!

@tomirons what do you think mate? There are a few minor things I'd change like renaming include_doccomments to include_doc_comments for readability, but overall I think it looks good?

[tomirons]

I like the concept of this feature.

For this to be merged, some tests will need to be written.

[Menkveld-24]

I've added some tests for the get request as well as the doc comment generation.
However, I stumbled upon deprecation of the Illuminate/Contracts/Validation/Rule used in the UppercaseRule. (https://laravel.com/api/10.x/Illuminate/Contracts/Validation/Rule.html) I think it's been replaced by the Illuminate/Contracts/Validation/ValidationRule. I left the check for the deprecated rule in there to not break it with the Rule.
Also phpunit kept complaining about the xml file and that it wanted me to run './vendor/bin/phpunit --migrate-configuration'
Also; there's still an error in the tests with the cache which i've been unable to resolve

[andreaselia]

Great updates, thank you @Menkveld-24!

I've been running into that issue too, it used to show up locally but not when running GitHub actions, so not sure what that's about. cc @tomirons 🤔

StyleCI appears to be failing but that's quite minor.