···5555Filters work only with the [experimental parser](#parser) which is currently an opt-in feature.
5656:::
57575858-If you work with large specifications and want to generate output from their subset, set `input.include` to a valid regular expression string.
5858+If you work with large specifications and want to generate output from their subset, set `input.include` to a regular expression string matching against resource references.
59596060```js
6161export default {
-20
docs/openapi-ts/output.md
···207207208208:::
209209210210-### Filtering Endpoints
211211-212212-If you only want to include specific endpoints in the generated services, you can use the `filter` config option to filter endpoints. The provided value should be a regular expression to match against endpoints with the `{method} {path}` pattern. For example, the config below will only include all `/api/v1/foo` endpoints.
213213-214214-```js
215215-export default {
216216- client: '@hey-api/client-fetch',
217217- input: 'path/to/openapi.json',
218218- output: 'src/client',
219219- plugins: [
220220- '@hey-api/schemas', // preserves default output
221221- '@hey-api/types', // preserves default output
222222- {
223223- filter: '^\\w+ /api/v1/foo$', // [!code ++]
224224- name: '@hey-api/services',
225225- },
226226- ],
227227-};
228228-```
229229-230210### Output
231211232212Below are different outputs depending on your chosen style. No services approach will not generate the `services.gen.ts` file.
+1-1
docs/sponsorship.md
···11## Sponsoring
2233-Love Hey API? Please consider becoming a [sponsor](https://github.com/sponsors/mrlubos).
33+Love Hey API? Please consider becoming a [sponsor](https://github.com/sponsors/hey-api).