ContributionsMost RecentMost LikesSolutionsRe: $ref: not being followed Sure. Thank you. I had to get rid of the yaml extension due to a constraint on what files can be loaded here. $ref: not being followed I had a OpenAPI file I found unwieldy so decided to break it up. It seemed pretty straightforward, but when I launch the UI (http://localhost:3000/api-docs/) I get: Speaker API 1.0.0 OAS 3.0 No operations defined in spec! Here is the top level file: openapi: 3.0.0 info: title: Speaker API version: 1.0.0 paths: /reload-data: $ref: './endpoints/reloadData.yaml' /select-speaker/{name}: $ref: './endpoints/selectSpeaker.yaml' /speaker-status/{speakerName}: $ref: './endpoints/speakerStatus.yaml' /set-browser-source-url: $ref: './endpoints/setBrowserSourceUrl.yaml' /get-speaker-data: $ref: './endpoints/getSpeakerData.yaml' /get-current-speaker: $ref: './endpoints/getCurrentSpeaker.yaml' /set-speaker-data-file-path: $ref: './endpoints/setSpeakerDataFilePath.yaml' Any suggestion how to fix or debug what's going on? Warm regards, Bob