From 0e597e94989f4c6d670ec88f5f8bb08c51ea9101 Mon Sep 17 00:00:00 2001 From: Esko Luontola Date: Mon, 20 Apr 2015 15:02:28 +0300 Subject: [PATCH] Fix broken include in Spring HATEOAS sample's API guide Closes gh-59 --- .../rest-notes-spring-hateoas/src/main/asciidoc/api-guide.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/samples/rest-notes-spring-hateoas/src/main/asciidoc/api-guide.adoc b/samples/rest-notes-spring-hateoas/src/main/asciidoc/api-guide.adoc index 0a1855b0..71227a70 100644 --- a/samples/rest-notes-spring-hateoas/src/main/asciidoc/api-guide.adoc +++ b/samples/rest-notes-spring-hateoas/src/main/asciidoc/api-guide.adoc @@ -64,7 +64,7 @@ use of HTTP status codes. Whenever an error response (status code >= 400) is returned, the body will contain a JSON object that describes the problem. The error object has the following structure: -include::{generated}/error-example/response-fields.adoc +include::{generated}/error-example/response-fields.adoc[] For example, a request that attempts to apply a non-existent tag to a note will produce a `400 Bad Request` response: