| commit | c3e4ad89f5af8ed312a8451e9c992047a79668b7 | [log] [tgz] |
|---|---|---|
| author | Bertrand Delacretaz <bdelacretaz@apache.org> | Wed Jun 03 11:12:58 2020 +0200 |
| committer | GitHub <noreply@github.com> | Wed Jun 03 11:12:58 2020 +0200 |
| tree | 8221174c59e8247f8ea8c4fe5fb0a88e7363abd1 | |
| parent | 71ef769e5564cf78e49d6679a3270ba8706ae406 [diff] |
Mention internal requests + tentative fluent API
This module is part of the Apache Sling project.
It provides mock implementations of the SlingHttpServletRequest, SlingHttpServletRepsonse and related classes.
These helpers can be used for testing, like the Sling Mocks do.
They are also useful for internal requests using the SlingRequestProcessor service, like in the GraphQL Core module which uses that technique to retrieve GraphQL schemas using the powerful Sling request processing mechanisms.
Internal requests using the SlingRequestProcessor service currently require a lot of boilerplate code, which we could remove by creating a fluent interface that manages the required request and response objects under the hood.
Maybe something like:
InternalRequest
.get(SlingRequestProcessor, ResourceResolver)
.forPath("/yocats")
.withSelectors("farenheit", "451")
.withExtension("json")
.execute()
.checkStatus(200)
.checkContentType("application/json")
.getContentAsStream();
This is just an idea so far...patches welcome, and maybe such an API doesn't belong in this module, but would just use its helpers.