You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just started using this package, like it so far, so thanks very much for your work!
Ran into the following, not sure if this is something I did wrong, but from reading the docs and the config file I think this shouldnt happen:
I've started to get this to work on one of our API endpoints, which is a POST endpoint. I've added some @bodyParam docs in the Request class, added the following to the AppServiceProvider:
if (class_exists(Scribe::class)) {
Scribe::bootstrap(function (GenerateDocumentation$command) {
App::setLocale('en');
});
Scribe::instantiateFormRequestUsing(function (string$form_request_class_name) {
if ($form_request_class_name === {{className}}::class) {
returnrequest()->createFrom(request(), new {{className}}(resolve({{dependency}}::class)));
}
});
}
This has resulted in a Postman collection json file which includes the following:
Although the config explicitly says the following:
/*
* The value of the parameter to be used by Scribe to authenticate response calls.
* This will NOT be included in the generated documentation.
* If this value is empty, Scribe will use a random value.
*/
So I was not expecting to see the actual api token in put in the config to show up in the Postman collection. Is this a bug, or did I misunderstand something?
Scribe version
4.22.0
PHP version
8.1.18
Framework
Laravel
Framework version
10.15.0
Scribe config
What happened?
Just started using this package, like it so far, so thanks very much for your work!
Ran into the following, not sure if this is something I did wrong, but from reading the docs and the config file I think this shouldnt happen:
I've started to get this to work on one of our API endpoints, which is a POST endpoint. I've added some
@bodyParam
docs in the Request class, added the following to the AppServiceProvider:This has resulted in a Postman collection json file which includes the following:
Although the config explicitly says the following:
So I was not expecting to see the actual api token in put in the config to show up in the Postman collection. Is this a bug, or did I misunderstand something?
Docs
The text was updated successfully, but these errors were encountered: