Closed codeodor closed 4 years ago
One more that I'm thinking about doing is adding a token to the attempts, so you can track each attempt back to someone who is not logged in. For example, if you send out an email to a bunch of people who are not users in your system, and give each one a random token, you can see who responded, what their response was, etc.
Although now that I think about it, that might not be necessary, since in your own app you can get params[:token] and tie it to some model, and make current_user
return that model, which then gets that info into the attempt. So never mind on that.
Thanks for this PR @codeodor I will rebase this and work on top of it
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs for another 14 days. Thank you for your contributions.
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs for another 14 days. Thank you for your contributions.
In case you approve of all of the pull requests I've opened today, I created a branch that merges them all together, since some have conflicting changes. (e.g., if you were to merge both editing a survey and the multitenancy support, editing a survey needs to be adjusted to pull from the owner surveys scope).