Error when generating documentation: Public properties value not found on Knuckles\Camel\Output\Parameter

[nlsnightmare]

• I confirm that I have read and attempted the tips in the Troubleshooting Guide.

What happened?

1. I set my configuration to the default configuration
2. Then I ran php artisan scribe:generate
3. But I saw the provided screenshot

The autogenerated documentation seems to kinda work still, althouth there are a few extra backticks in the end of the bash commands (screenshots bellow).
Also, a few requests seem to return exceptions such as "invalid signature", or "xxx not found". These are not too much of a big deal however, since I can manually override them

Screenshots and stack traces:

My environment:

• PHP version (from php -v): PHP 8.0.6 (cli)
• Framework (Laravel/Lumen): Laravel
• Laravel/Lumen version (from composer show laravel/framework or composer show laravel/lumen-framework): 8.47.0
• Scribe version (from composer show knuckleswtf/scribe): 3.0.2

My Scribe config (minus the comments):

Additional info:

[shalvah]

Do you have any custom strategies? Seems like a case of old code (v2, 'value') instead of new (v3, 'example').

[nlsnightmare]

No, it it's a vanilla, freshly installed version. I have however modified a few Laravel things, and some exceptions are thrown while generating the documentation. As a sidenote, after disabling postman and openapi generation it works fine for me. I can of course keep providing feedback if you'd like to, but for me the problem is solved, and I'd be ok with closing this issue. Στις Παρ, 18 Ιουν 2021, 2:27 μ.μ. ο χρήστης Shalvah < ***@***.***> έγραψε:

…

Do you have any custom strategies? Seems like a case of old code (v2, 'value') instead of new (v3, 'example'). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#246 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEYGUWL6YHMQYH36B6HNJQLTTMUQZANCNFSM465KKVMQ> .

[shalvah]

Thank you, that was helpful. If you can update to 3.1.0, it should be fixed now.

[nlsnightmare]

I can indeed confirm that it works like a charm! Thanks a lot!