Skip to content

Issues: fullcube/loopback-component-access-groups

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.

Sign up for GitHub

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

12 Open 8 Closed
12 Open 8 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

An in-range update of supertest is breaking the build 🚨 greenkeeper
#39 opened Sep 6, 2018 by greenkeeper bot
3
User can create Invoices for different groups
#35 opened Jan 31, 2018 by hbbh
An in-range update of chai is breaking the build 🚨 greenkeeper
#28 opened Aug 5, 2017 by greenkeeper bot
2
using custom user persisted model, insted of User Built-in model not working
#21 opened May 4, 2017 by saikatharryc
2
Support for LoopBack 3.x
#19 opened Mar 27, 2017 by ivanschwarz
4
Allow for multiple group models
#17 opened Jan 8, 2017 by yotamsha
1
getCurrentContext
#16 opened Oct 13, 2016 by k1ng440
3
Bypass all access control for certain users
#15 opened Sep 28, 2016 by bostondv
4
Crash with mongodb connector due to getCurrentContext()
#12 opened Aug 7, 2016 by GregAujay
6
this.getCurrentUser returns wrong user
#10 opened Jun 2, 2016 by benjaminhaven
1
Undocumented access control bypass mechanisms
#8 opened Mar 18, 2016 by RossWilliams
GroupAccessModel should be created automatically if it doesn't exist
#5 opened Feb 9, 2016 by mrfelton
1
ProTip! Add no:assignee to see everything that’s not assigned.