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.

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

Authorization structure for Frontend #12

Open
4 tasks
mistikk opened this issue Sep 13, 2018 · 1 comment
Open
4 tasks

Authorization structure for Frontend #12

mistikk opened this issue Sep 13, 2018 · 1 comment
Assignees
Projects
Milestone

Comments

@mistikk
Copy link
Member

mistikk commented Sep 13, 2018

This will for all components.

AC (acceptance criteria)

  • We will create HOC for Authorization.
  • Every parent component will has permission. We will check with customer permission with component permissions.
  • We should get user data from api if page is refreshed and we should set to redux.
  • Permission control can be inside of parent component. For example, a role can see list of offer but can not delete
@mistikk mistikk added this to the Sprint 1 milestone Sep 13, 2018
@mistikk mistikk self-assigned this Sep 13, 2018
@ue ue added this to TODO in Board Sep 13, 2018
@ue
Copy link
Member

ue commented Sep 14, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Board
  
TODO
Development

No branches or pull requests

2 participants