Skip to content

[Feature Request] Support different connection character between instanceName and file suffix #1998

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
slhmy opened this issue Apr 7, 2025 · 0 comments

Comments

@slhmy
Copy link

slhmy commented Apr 7, 2025

Is your feature request related to a problem? Please describe.
For json & yaml file, . will be better than _ to be the connection characer of the filename.
(Currently these files look like ${instanceName}_swagger.json)
I want files like ${instanceName}.swagger.json because they works better in VSCode with swagger extensions, files with .swagger.json or .swagger.yaml suffix can be automatically binded while _swagger.json or _swagger.yaml will not.

Describe the solution you'd like
An additional cli parameter to change connection character from _ to . .

Describe alternatives you've considered
Use . as the connection character for json and yaml files, continue using _ as the connection character for go files.

Additional context
😶‍🌫️ NOTING HERE...

@slhmy slhmy changed the title Support different connection character between instanceName and file suffix [Feature Request] Support different connection character between instanceName and file suffix Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant