You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 8, 2018. It is now read-only.
I assume we do not need "email" field and "used" should be reference to participant when it was used or null if not.
I do not see any reason to use "email" field - invites could be printed and given in some prior events/meetup/hackathons as prizes, so we do not know email who will use this invite.
What if I want to restrict invite to some specific email address? Also probably it's reasonable to save invite creator and notify him once invite is used.
So email is email restriction? ok.
email restriction and notifications could be nice features to have... may be as separate [FR]
but for used - its better to change the way I've described.
Implement $sbj.
DB structure for it already exists.
Table is
gdg_invites
and it contains following values:(
code
= 32 chars,email
,event_id
,used
)The text was updated successfully, but these errors were encountered: