fern
fern copied to clipboard
Ability for audience filters to be exclusive (not just inclusive)
Problem description
Currently, using audiences to filter an API is inclusive: the resulting APIs have the specified audience. There is no way to have an audience be an exclusive filter so that all my API endpoints do not need to be labeled.
Why would it be useful?
I may want to just label a few endpoints with a different audience/segment than the rest of my APIs so it would be convenient to allow filters to be exclusive: "filter my API to all endpoints that are NOT beta" for example.
Additional context
Maybe I'm trying to fit a square peg into a round hole here. My aim is to use a single API yaml file with different audiences and try to create separate tabs for the api reference in the docs.