Skip to content

Fix capabilities weren't detected correctly #13368

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 31, 2018
Merged

Conversation

tsteur
Copy link
Member

@tsteur tsteur commented Aug 29, 2018

No description provided.

@mattab mattab added this to the 3.7.0 milestone Aug 30, 2018
@mattab mattab added Bug For errors / faults / flaws / inconsistencies etc. Needs Review PRs that need a code review labels Aug 30, 2018
@diosmosis
Copy link
Member

Should there be a test for this?

@tsteur
Copy link
Member Author

tsteur commented Aug 30, 2018

I reckon it's fine. It is not really easily testable since in UI tests we mostly use FakeAccess for example. Could put it in a protected function or so if needed and test it possibly.

@diosmosis
Copy link
Member

diosmosis commented Aug 30, 2018

Could be in an integration test for Access? I haven't checked if it's possible of course.

@tsteur
Copy link
Member Author

tsteur commented Aug 31, 2018

Sorry somehow thought it was in a controller. Done

@diosmosis diosmosis merged commit 2a3b1e8 into 3.x-dev Aug 31, 2018
@diosmosis diosmosis deleted the capabilitydetection branch August 31, 2018 22:55
@mattab mattab modified the milestones: 3.7.0, 3.6.1 Sep 1, 2018
InfinityVoid pushed a commit to InfinityVoid/matomo that referenced this pull request Oct 11, 2018
* Fix capabilities weren't detected correctly

* added test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Needs Review PRs that need a code review
Development

Successfully merging this pull request may close these issues.

3 participants