Skip to content
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

server generate : can't run custom template in operationGroups #1290

Closed
fredbi opened this issue Dec 1, 2017 · 3 comments
Closed

server generate : can't run custom template in operationGroups #1290

fredbi opened this issue Dec 1, 2017 · 3 comments

Comments

@fredbi
Copy link
Contributor

fredbi commented Dec 1, 2017

Problem statement

Defined a custom template.
Declared it in the config YAML section 'operation_groups:'
Run server generate on this config

Nothing happens! The generator found an operation group but didn't take template into account.
Retesting with a wrong source template name indicates that there is not even an attempt to load the template.

Will fix this with a P.R as soon as the regression on security items allows a CI based on current master to run...

Cheers,

Fred

Environment

swagger version: 0.12
go version: 9.1
OS: Linux

@fredbi
Copy link
Contributor Author

fredbi commented Dec 5, 2017

Merged with 1290-fix server generation now supports operationGroups templates jus… #1298

@fredbi fredbi closed this as completed Dec 5, 2017
@ZachEddy
Copy link
Contributor

ZachEddy commented Dec 13, 2017

Hi there! I also stumbled across this issue using Homebrew.

# after following homebrew instructions and freshly installing go-swagger
swagger version
version: 0.13.0
commit: 8135eb6728e43b73489e80f94426e6d387809502

I had problems with operationGroups and using custom templates. However, using go get to install go-swagger instead of Homebrew fixed the issue.

Not sure if Homebrew is supposed to use the latest and most up-to-date version of go-swagger (i.e. I don't know if it has your recent fix), but I thought I'd bring it up just in case.

@casualjim
Copy link
Member

this fix came in after the 0.13 release but will be included in the next release

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

3 participants