Interesting - would you mind adding an example of this to internal/test?

I've not hit this before, but would be good to see what we're missing

@jamietanna Thank you for the swift review! I agree and removed config flag and enabled it by default. I also added an example to internal/test for overlay.

Apparently the issue only occurs if the spec is in a diffent directory then the one oapi-codegen is invoked from. Therefore I put the spec.yaml into the subdirectory spec/. Running go generate after setting ResolveRefs to false reproduces the error.

@jamietanna Is the example sufficient or do you need more information? :)

Thanks very much for this @jgraeger - this was a good catch, and I'm classing this as a bug, not a feature 😅

I've pushed a couple of tweaks - will wait for CI then merge

Main tweaks:

• no longer making it opt-in, and instead default behaviour
• moving the test to a different directory - you weren't expected to know this, and this is more my personal preference, what you'd done was absolutely great - thank you!

Tried this fix on my side and it works well! Is there any ETA for this release @jamietanna? Thanks!