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
Currently, the language on the importer is very broken:
Expected Behavior
In the screenshot above, I expect the language to read 1 donor will be created 7 donations will be imported 6 duplicate donors detected
Steps to Reproduce
Import a CSV, and select "dry run"
This is the output.
Possible Solution
Since it's primarily dry run functionality that is making confusing language, switch to modal tense would have on processes that did not run (like imports and creation) and simple past tense for the "detected" ones.
@Benunc Since these messages appear directly above the Start Import button, I have adjusted the strings to future tense so they describe what will happen when the import is started.
@Sidsector9 Please move forward with the string replacements above and ping me for review on this one.
kevinwhoffman
changed the title
fix: clean up language on the importer for dry runs
Clarify language of Dry Run messages
Sep 19, 2018
Current Behavior
Currently, the language on the importer is very broken:
Expected Behavior
In the screenshot above, I expect the language to read
1 donor will be created
7 donations will be imported
6 duplicate donors detected
Steps to Reproduce
Possible Solution
Since it's primarily dry run functionality that is making confusing language, switch to modal tense
would have
on processes that did not run (like imports and creation) and simple past tense for the "detected" ones.detected
will be created
will be created
detected
will be imported
Acceptance Criteria
The text was updated successfully, but these errors were encountered: