Doichain/dapp

If you re-request an already confirmed email, nothing happens

Open

#30 opened on Jun 19, 2018

View on GitHub
 (0 comments) (0 reactions) (2 assignees)JavaScript (13 forks)auto 404
enhancementhelp wantedquestion

Repository metrics

Stars
 (6 stars)
PR merge metrics
 (PR metrics pending)

Description

in this case I expect the following:

  1. which attributes has a successful DOI? Which of those attributes do not comply.
  • doesn't it have a block?
  • is it confirmed?
  • is it in the local database?
  • is it available in the memcash
  • does it have an error (e.g. problems with funding or other setup problems)

  1. in case DOI is not yet confirmed - I possibly want another DOI request email It's preferable to send out this information email from Alice directly. with an information about the confirmation status, nameId and possibility to unsubscribe.

  2. in case DOI is confirmed - I want an email that I confirmed the DOI already Alice sends out a simple information email about this fact.

Contributor guide

Research direction
Investigate the email confirmation flow. Trace the handler that triggers email resend when user re requests an already confirmed email. Determine why no action occurs and implement appropriate behavior based on confirmation status.
Tech stack
javascriptnodejsmongodb
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
JavaScriptMeteor.jsMongoDB
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60