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

marcjansen / shogun2 / 113
54%
master: 55%

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

pending completion
113

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%)

1.09 hits per line

Jobs
ID Job ID Ran Files Coverage
1 113.1 29 Jan 2018 11:08AM UTC 0
54.29
Travis Job 113.1
2 113.2 29 Jan 2018 11:08AM UTC 0
54.29
Travis Job 113.2
Source Files on build 113
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #113
  • 7311458f on github
  • Prev Build on optionally-restrict-rest-output (#92)
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