7
75%
develop: 75%

Ran 25 Jul 2018 11:37PM UTC

Files 186

Run time 15s

Badge

Embed ▾

Committed 25 Jul 2018 11:06PM UTC coverage: 14.502% (+0.07%) from 14.435%

Job # TESTING_PROFILE=unit-tests

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

Add endpoint for users to get their actions (#1638)

* Add endpoint for users to get their actions

#1589

The issue in the ticket was because the UI was comparing
the GitHub username with the Google email address that came back from
the permissions call. That, plus the fact that I had forgotten about
SAM's support for groups, means we do need an endpoint to indicate
the actions a user can perform on workflow.

I had this before, with OPTIONS operations on a few API calls, but it
was clunky and overkill, so I've added a new endpoint,
`/path/workflow/{repository}/actions`, that returns the actions a user
can perform on a workflow.

The issue with groups is that a user can be given permissions to a
resource through a group -- in that case the user's individual email
will not show up in the list of permissions. So we could not tell
client-side what a user's permissions are just by reading the email
addresses.

Also:

* Added Not Implemented to state changing operations in
NoOpPermissionsImpl, just in case it gets turned on and somebody
tries to use it.

Run Details

1800 of 12412 relevant lines covered (14.5%)

0.29 hits per line

ga4gh / dockstore / 5755 / 7
75%
develop: 75%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 5755.7 (TESTING_PROFILE=unit-tests)

ga4gh / dockstore / 5755 / 7 75% develop: 75%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 5755.7 (TESTING_PROFILE=unit-tests)

ga4gh / dockstore / 5755 / 7
75%
develop: 75%

README BADGES
x