marcjansen / shogun2

54%

master: 55%

LAST BUILD ON BRANCH optionally-restrict-rest-output

branch: optionally-restrict-rest-output

CHANGE BRANCH

x

Reset

• optionally-restrict-rest-output
• archetypo
• coverall-badge
• fewer-peter
• find-bugs
• getter-harmonisation
• intercept-wps
• interceptor-adjustments
• interceptorpost
• irregular-names
• language-in-release-notes
• logo-in-readme
• logo-minors
• master
• model-review
• mv-release-doc
• null-safe-resultset
• plugin-deletion
• prepare-interceptor-beans
• proxy-minors
• reenable-coveralls
• replacements
• switch-to-jacoco
• test-overhaul

Build # 113

Build Type

push

travis-ci

Committed by marcjansen

Commit Message

Allow configurable sparse output of REST GET requests

This adds the possibility to optionally get a sparse result from
REST get calls against the abstract REST controller. This can be
usefull if you are not interested in the complete representation
of objects, but only certain fields are important for you.

In order to only get e.g. the fields `name` and `id` of all
entities `TestEntity` (mapped to `/rest/testentity`): the
following request can be used:

    /rest/testentity?output:only=name,id

All other fields of the returned objects will be `null`.

This can be combined with the existing `filter`-API:

    /rest/testentity/filter?id=42&output:only=name,id

The above will give you back the sparse `TestEntity` serialisation
where only the fields `name` and `id` have real values, others are
`null`.

This implementation is backwards compatible for the REST API.

Run Details

1922 of 3540 relevant lines covered (54.29%)

1.09 hits per line