-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Applicant
and /applicants/*
endpoints
#798
Conversation
558b729
to
6a82e33
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #798 +/- ##
==========================================
- Coverage 92.79% 92.47% -0.32%
==========================================
Files 94 91 -3
Lines 1498 1422 -76
Branches 226 214 -12
==========================================
- Hits 1390 1315 -75
+ Misses 102 101 -1
Partials 6 6 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! There is a small bit of malformed sample data in the tests.
I also notice that this PR doesn't release the proposal_submitter_email
requirement on bulk uploads, even though it's no longer used for anything. Totally fine if you want to consider that a follow-up downstream effect, but let me know if that's the case or if it was an oversight.
Should be a quick re-review!
e9cb673
to
42a9178
Compare
@@ -197,16 +196,6 @@ const assertBulkUploadCsvIsValid = async (csvPath: string): Promise<void> => { | |||
await assertCsvContainsRowsOfEqualLength(csvPath); | |||
}; | |||
|
|||
export const getApplicantEmailFieldIndexForBulkUpload = async ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See here for removal of theproposal_submitter_email
stuff @reefdog
Just checking... I thought that was taken out? Did I miss something? |
When I tested it locally against the front-end, I received UI errors that I traced back to log output from the service saying the email was required. Let me re-run that now to verify… Okay yup, confirmed, on this branch submitting a CSV without that field returns an error:
|
2020d04
to
0556d19
Compare
ec750ac
to
72a86f9
Compare
@reefdog ahh I see it now; ok thanks, that should be fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works! 🎉 Thanks. Does package.json need its version bumped, too?
The concept of applicant never really got used, and we now know that proposal data may or may not be associated with an applicant in the PDC. We also know that applicants are ONLY organizations at this stage of the PDC, and a proposal might actually be associated with more than one. For these reasons we are removing the concept of an applicant, and removing the requirement that an applicant be defined in order for a proposal to be created. Issue #777 Allow access to a new /organizations endpoint
72a86f9
to
789ef97
Compare
The other PR talked about this too but we'll be taking version out of package.json (#807) |
This field is no longer required by the API[1], so we can stop telling users it’s required. [1] PhilanthropyDataCommons/service#798 Issue #690 Remove `proposal_submitter_email` bulk upload requirement
This PR removes the concept of an Applicant from the PDC, along with the endpoints and entity associations.
Related to #777
Related to #730
Note this is built off of #794 and shouldn't be merged until after that PR is merged