We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello everyone, I am using two routes with different middlewares so I coded them like this in routes/api.php.
`Route::post('delivery-status', 'API\DeliveryStatusController@store')->middleware('token1.auth');
Route::get('delivery-status', 'API\DeliveryStatusController@index')->middleware('token2.auth');`
Now, I want to show only the get method route(2nd one) in the apidoc and exclude the post one. Can anyone suggest me how to do this?
Also, mentioning the api in exclude section in configuration removes both of them from the doc. I have tried all of these but none of them worked-:
"exclude" => ['deliveryStatuses.store],['delivery-status.store'],['delivery-statuses.store'],['delivery_status.store'],,['deliveryStatus.store'],['delivery_statuses.store']
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello everyone,
I am using two routes with different middlewares so I coded them like this in routes/api.php.
`Route::post('delivery-status', 'API\DeliveryStatusController@store')->middleware('token1.auth');
Route::get('delivery-status', 'API\DeliveryStatusController@index')->middleware('token2.auth');`
Now, I want to show only the get method route(2nd one) in the apidoc and exclude the post one.
Can anyone suggest me how to do this?
Also, mentioning the api in exclude section in configuration removes both of them from the doc.
I have tried all of these but none of them worked-:
"exclude" => ['deliveryStatuses.store],['delivery-status.store'],['delivery-statuses.store'],['delivery_status.store'],,['deliveryStatus.store'],['delivery_statuses.store']
The text was updated successfully, but these errors were encountered: