Skip to content
New issue

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

Ability for audience filters to be exclusive (not just inclusive) #4751

Open
magaldima opened this issue Sep 25, 2024 · 0 comments
Open

Ability for audience filters to be exclusive (not just inclusive) #4751

magaldima opened this issue Sep 25, 2024 · 0 comments
Labels
CLI Fern's Command line interface fern definition Defining your API in Fern's YAML format openapi Importing or exporting OpenAPI/Swagger specs

Comments

@magaldima
Copy link

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.

@dannysheridan dannysheridan added fern definition Defining your API in Fern's YAML format openapi Importing or exporting OpenAPI/Swagger specs CLI Fern's Command line interface labels Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLI Fern's Command line interface fern definition Defining your API in Fern's YAML format openapi Importing or exporting OpenAPI/Swagger specs
Development

No branches or pull requests

2 participants