Skip to content
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

Jump to bottom

Setting route permissions via the registry doesn't work #2297

Closed
brent-hoover opened this issue May 17, 2017 · 2 comments
Closed

Setting route permissions via the registry doesn't work #2297

brent-hoover opened this issue May 17, 2017 · 2 comments
Assignees
@michael-alade
Labels
bug For issues that describe a defect or regression in the released software verified reproducible For issues that describe bugs that the core team was able to confirm

Comments

@brent-hoover
Copy link
Collaborator

Expected behavior

You should be able to specify permissions/audience in a route in register.js and have it take affect.

Actual Behavior

It doesn't work, you need to programmatically add these.

Steps to Reproduce the Behavior

  1. Create a plugin with a route (you could use the reaction-example-plugin as a starting point).
  2. Add permissions to the route according to the documentation
  3. Observe you still get an error
@brent-hoover brent-hoover added the bug For issues that describe a defect or regression in the released software label May 19, 2017
@michael-alade michael-alade self-assigned this Jun 2, 2017
@michael-alade
Copy link

michael-alade commented Jun 2, 2017 •
edited
Loading

I was able to reproduce this bug. And I have opened a WIP PR for it.

@michael-alade michael-alade mentioned this issue Jun 2, 2017
Merged
@michael-alade michael-alade added the verified reproducible For issues that describe bugs that the core team was able to confirm label Jun 2, 2017
@aaronjudd
Copy link
Contributor

Closed in #2388

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michael-alade michael-alade

Labels
bug For issues that describe a defect or regression in the released software verified reproducible For issues that describe bugs that the core team was able to confirm
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@brent-hoover @aaronjudd @michael-alade