panic: invalid character '\n' in string literal in go-swagger-merger v0.3.0 (worked in v0.0.0-20220614083330-a4837be9dd7c)

[ShivaliBandi]

Hi team,

We're encountering a runtime panic when running go-swagger-merger with version v0.3.0. The same input files and setup were working correctly with the older commit version:
v0.0.0-20220614083330-a4837be9dd7c.
Error Trace:
panic: invalid character '\n' in string literal

goroutine 1 [running]:
main.main()
/root/go/pkg/mod/github.com/g3co/go-swagger-merger@v0.3.0/main.go:20 +0x167
Environment:
Go version: go1.21.x

OS: RHEL 8.10

go-swagger-merger version: v0.3.0 (breaking)

Previously working version: v0.0.0-20220614083330-a4837be9dd7c
Request:
Could you please help identify what's changed between these versions that may be causing this panic? Let me know if I can provide a minimal reproduction or any of the input Swagger files.

Thanks in advance!
Shivali

[g3co]

Hi @ShivaliBandi, sorry about that. The new version has drastically changed; it uses a recursive approach to merge files, and it provides support for JSON files.

Could you please provide input files if they can be shared here? It will help track the issue quickly

[ShivaliBandi]

Thanks for the update!

Unfortunately, I can't share the actual input files due to internal policy. However, here are some details that might help:

The files are OpenAPI 3.0 compliant JSON objects, each with info, paths, and components.

No top-level arrays or circular references.

The command used is:

go-swagger-merger -o merged.yaml file1.json file2.json file3.json
Error seen:

panic: invalid character '\n' in string literal
This issue started appearing with v0.3.0. The same input worked fine on commit v0.0.0-20220614083330-a4837be9dd7c.

I’ll try to create a sanitized test case that reproduces the issue and will share it here if successful. Let me know if there’s any specific structure or debug flag you’d like me to try in the meantime.

Thanks again for your support!

[ShivaliBandi]

@g3co is there any update on this ?
Can you please try to resolve this or help me out to resolve this as soon as possible

[g3co]

Hi @ShivaliBandi, unfortunately, I couldn't reproduce the issue. But regarding the error caused by the wrong json/yaml file formatting. If it is possible, could you please share at least part of your source file with '\n' symbol in a string literal?

[g3co]

For immediate mitigation, could you please fix the previous working version v0.0.0-20220614083330-a4837be9dd7c in your go.mod file? There are no security updates or any critical changes in the newer version.