swagger-api/swagger-codegen

[typescript\angular2] Deal with 201 response status

Open

#4,397 opened on Dec 14, 2016

View on GitHub
 (10 comments) (1 reaction) (0 assignees)HTML (5,474 forks)batch import
Client: TypeScriptIssue: Bughelp wanted

Repository metrics

Stars
 (12,701 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Description

Currently, typescript\angular2 api.service.mustache template handles 204 responses status in order return an undefined value directly instead of call a response.json:

return this.createWithHttpInfo(user, passwd, extraHttpRequestParams)
            .map((response: Response) => {
                if (response.status === 204) {
                    return undefined;
                } else {
                    return response.json();
                }
            });

I've implemented an JAXRS RESt endpoint like this:

@Override
	public Response create(String username, String passwd) throws UsernameAlreadyExistsCommtyException, RepositorySystemException {
		String userId = this.userService.create(username, passwd);
		return Response.created(this.uriInfo.getAbsolutePathBuilder().path(userId).build()).build();
	}

As you can see, this method returns an create-201 response status code. So, there's no content inresponse's body. Instead, there's a location header.

Could you provide an straightforward approach to deal with this?

Swagger-codegen version

2.2.3-SNAPSHOT

Contributor guide