Actions
Patch #12078
closedUser#allowed_to? should return true or false
Status:
Closed
Priority:
Low
Assignee:
Category:
Code cleanup/refactoring
Target version:
Start date:
Due date:
% Done:
0%
Estimated time:
Description
The attached patch fixes a minor bug in User.allowed_to?
Specifically, that method should return a boolean, but it actually sometimes returns a Role instead. This is because .detect is used when really .any? should be used.
I am not aware of this causing any serious issues, but I noticed this during debugging and was greatly confused when allowed_to? suddenly returned a Role ;).
Files
Updated by Etienne Massip about 12 years ago
- Category set to Code cleanup/refactoring
Updated by Jean-Philippe Lang about 12 years ago
- Subject changed from Replace incorrect uses of .detect by .any? to User#allowed_to? should return true or false
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Target version set to 2.2.0
Committed in r10614. Another change was required so that User#allowed_to?
return true or false and tests were updated.
Actions