Invite users to private communities

[trex]

Frontend

• From Group component, a user can invite user by email
• From the user's account page you can view Groups that you have been invited to
  • A user can accept invitations to Groups they have been invited to

Backend

• Mutation invites a user to a group
• Mutation accepts invite
• Users receive email notification when invited to private community
  • Email is sent to invited existing user, prompting them to login and accept the invite
  • Email is sent to invited non-existing user, prompting them to create an account and join the group
    • User is added to all groups they are invited to upon registration

Design

• Design email template for community invitations

[trex]

@ZacharyRose I pushed some changes to the invite-users branch of the server last night. The inviteUserToGroupByEmail and acceptGroupInvite mutations were returning a boolean rather than Group, which did not match the GraphQL schema. They are both now returning the group related to the groupId parameter passed in.

Can we add a required String parameter, message, to the inviteUserToGroupByEmail mutation, so that a message from the user extending the invitation is passed along in the email to the invited person to build trust in accepting the invite?

[trex]

@ZacharyRose I pushed changes to the invite-users branch on hawthorn-server to update the inviteUserToGroupByEmail mutation interface to:
inviteUserToGroupByEmail(groupId: ID!, email: String!, customMessage: String!): Group!

These changes add a new table to the database for modeling the outstanding group invitations. You will need to run prisma deploy from the command line to run the database migrations to add the table and generate an updated javascript prisma client.

[trex]

@ZacharyRose I finished up the backend changes for this issue, pushed to the invite-users branch (codefordenver/hawthorn-server#9).

I know we are holding on building more onto the frontend until design is ironed out and the atomic component architecture is in place. However, people have started signing up for accounts and I would like to add these features to the frontend ASAP so that we can have a meaningful user experience in the application. Can we add these components to the frontend now and refactor when the design and architecture is ironed out?

[zacksabbath]

Hey Trevor, yes I will look at that tonight.

…

On Thu, Mar 12, 2020 at 11:48 PM trevor smith ***@***.***> wrote: @ZacharyRose <https://github.com/zacharyrose> I finished up the backend changes for this issue. I know we are holding on building more onto the frontend until design is ironed out and the atomic component architecture is in place. However, people have started signing up for accounts and I would like to add these features to the frontend ASAP so that we can have a meaningful user experience in the application. Can we add these components to the frontend now and refactor when the design and architecture is ironed out? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADM7Q42LQ7BFL24OAEM3KMDRHHCMJANCNFSM4KI6WUIA> .