···8899Input filters now avoid generating invalid output without requiring you to specify every missing schema as in the previous releases. As part of this release, we changed the way filters are configured and removed the support for regular expressions. Let us know if regular expressions are still useful for you and want to bring them back!
10101111-::: code-group
1212-1313-```js [include]
1111+```js
1412export default {
1513 input: {
1614 // match only the schema named `foo` and `GET` operation for the `/api/v1/foo` path
···2927 plugins: ['@hey-api/client-fetch'],
3028};
3129```
3232-3333-```js [exclude]
3434-export default {
3535- input: {
3636- // match everything except for the schema named `foo` and `GET` operation for the `/api/v1/foo` path
3737- exclude: '^(#/components/schemas/foo|#/paths/api/v1/foo/get)$', // [!code --]
3838- filters: {
3939- operations: {
4040- exclude: ['GET /api/v1/foo'], // [!code ++]
4141- },
4242- schemas: {
4343- exclude: ['foo'], // [!code ++]
4444- },
4545- },
4646- path: 'https://get.heyapi.dev/hey-api/backend',
4747- },
4848- output: 'src/client',
4949- plugins: ['@hey-api/client-fetch'],
5050-};
5151-```
5252-5353-:::
+5
.changeset/moody-socks-develop.md
···11+---
22+'@hey-api/openapi-ts': patch
33+---
44+55+fix(parser): handle exclusiveMinimum and exclusiveMaximum in OpenAPI 3.1.x when they're 0