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

marcjansen / shogun2 / 113 / 1
54%
master: 55%

Build:
Build:
LAST BUILD BRANCH: proxy-minors
DEFAULT BRANCH: master
Ran 29 Jan 2018 11:08AM UTC
Files 160
Run time 5s
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

29 Jan 2018 11:02AM UTC coverage: 54.294% (-0.8%) from 55.098%
113.1

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.

1922 of 3540 relevant lines covered (54.29%)

0.54 hits per line

Source Files on job 113.1
  • Tree
  • List 0
  • Changed 51
  • Source Changed 30
  • Coverage Changed 50
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 113
  • Travis Job 113.1
  • 7311458f on github
  • Prev Job for on optionally-restrict-rest-output (#92.3)
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