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

Accounts with both isOrganizer and isVolunteer flags set have strange behavior #616

Open
utunga opened this issue May 22, 2020 · 1 comment
Open

Accounts with both isOrganizer and isVolunteer flags set have strange behavior #616

utunga opened this issue May 22, 2020 · 1 comment

Comments

@utunga
Copy link
Contributor

utunga commented May 22, 2020

Specifically #612 and #610 are both examples of bugs that occur if you do this.

Steps to reproduce

  1. Go into firebase back end
  2. Find a relevant account in users table
  3. Set flag 'isOrganizer=true' and also set 'isVolunteer=true'

Expected behavior

You can accept and start missions

Actual behavior

Per descriptions in both #612 and #610 this is not possible.
@DrewThomasCorps
Copy link
Contributor

I just tried this and it appears to be working for me on both localhost when running npm run start, and on the staging site. Could anyone else replicate this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@utunga @DrewThomasCorps