• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

marcjansen / shogun2 / 91 / 2
54%
master: 55%

Build:
Build:
LAST BUILD BRANCH: proxy-minors
DEFAULT BRANCH: master
Ran 07 Mar 2017 04:59PM UTC
Files 149
Run time 7s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

07 Mar 2017 04:55PM UTC coverage: 56.244% (-1.0%) from 57.198%
91.2

push

travis-ci

marcjansen
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.

1626 of 2891 relevant lines covered (56.24%)

0.56 hits per line

Source Files on job 91.2
  • Tree
  • List 0
  • Changed 6
  • Source Changed 6
  • Coverage Changed 6
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 91
  • Travis Job 91.2
  • 3093ed25 on github
  • Prev Job for on optionally-restrict-rest-output (#85.2)
  • Next Job for on optionally-restrict-rest-output (#92.2)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc