include and exclude based on paths

[RevanthGovindan]

Added configs for include or exclude specification paths based on config provided

[robertmassaioli]

Hi @RevanthGovindan , thanks for the PR submission for this feature request. Can you let me know why the includeTags and excludeTags feature does not work for your use case?

[RevanthGovindan]

@robertmassaioli includeTags and excludeTags works well, consider if someone wants to exclude or include any specific API, we may need this feature.

[robertmassaioli]

@RevanthGovindan If somebody only wants to include/exclude a specific API then they can just tag/untag APIs that way. I'm still not understanding why we need an extra feature to accomplish the same thing? Could you expand on your use case a little more?

[RevanthGovindan]

@robertmassaioli consider if someone wants to ignore API in Included tag, so this might be helpful.

[RevanthGovindan]

@robertmassaioli I have two different microservices, admin and customer module which has same tag called Login and it has API's as below, here Login tag is common for both microservices, but only login API is common i want to ignore account/get-customer from admin module, so this addition could be helpful to filter that. Admin Login:

1. account/login
2. account/get-customer

Customer Login:

1. account/get-details
2. account/get-bills

[Fimeo]

This could be really usefull for me too ! Exclude by (path name, method) couple by configuration let's our openapi generation without tag customisation.