Closed eelco2k closed 3 weeks ago
that was great update, mate. i will review it ASAP
Hey @eelco2k , Thank for your contribution! 😄 . I Have some question & suggestion.
if we want to use it, transformer of the resource must be created, right?
Please update documentation about it.
and i think it better to use default Filament Resource namespace instead of creating new Virtual namespace
assume we have a App\Filament\Resources\BlogResource
. Store the documentation into app\Filament\Resource\BlogResource\Api\Docs
I made the Virtual folder because swagger generator goes alphabetically through all files. If you would put the api files per resource it’s more probe to faults because it also look to the non Api folders as well. Other suggestions I will update after my vacation Thank you for your review and time.  if we want to use it, transformer of the resource must be created, right? Please update documentation about it. and i think its better to use default Filament Resource namespace instead of creating new Virtual namespace assume we have a App\Filament\Resources\BlogResource. Store the documentation into app\Filament\Resource\BlogResource\Api\Docs
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
@rupadana i've updated the readme and other files.
any updates on merging this PR?
Rough work on Swagger API Docs generator CLI command with stubs.
improvements are always welcome.