You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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...
The text was updated successfully, but these errors were encountered:
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
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...
The text was updated successfully, but these errors were encountered: