Skip to content
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

add mandatory fields for partner profile #3691

Merged

Conversation

fchatterji
Copy link
Contributor

@fchatterji fchatterji commented Jun 25, 2023

Resolves #2979

Description

Added mandatory fields to the partner profile model, only on validation context edit
Added tests and fixed failing test

Branch is based off #3651, to take advantage of the new validation context

Type of change

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update

How Has This Been Tested?

Added tests

Screenshots

image

@fchatterji fchatterji force-pushed the mandatory_fields_for_partner_profile branch from cf56c5c to 00d5c72 Compare June 26, 2023 15:57
@fchatterji fchatterji force-pushed the mandatory_fields_for_partner_profile branch from 00d5c72 to cfc0944 Compare June 26, 2023 15:58
@fchatterji fchatterji changed the title WIP: add mandatory fields for partner profile add mandatory fields for partner profile Jun 26, 2023
@cielf
Copy link
Collaborator

cielf commented Jun 29, 2023

@fchatterji I don't have the cycles to do a proper review tonight, but looking at the issue (which I wrote over a year ago and have learned so much since) -- I need to make sure that we are paying attention to the difference between saving the profile and submitting it for approval -- that the fields are not mandatory until being submitted for approval.

@fchatterji
Copy link
Contributor Author

Hey @cielf, well this branch is based off #3651, so it uses the same logic: the validation is checked at save and at approval.

So the same as the social network validation on #3651.

We could change it, but it's maybe better to first change it on the other branch? That way I can rebase off it, and we avoid conflicts.

Copy link
Collaborator

@dorner dorner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good! Unfortunately we can't merge it until my PR is also merged. :(

@awwaiid
Copy link
Collaborator

awwaiid commented Jul 28, 2023

@dorner which PR is this blocked on?

@awwaiid
Copy link
Collaborator

awwaiid commented Jul 28, 2023

Oh #3651, which is merged!

@cielf
Copy link
Collaborator

cielf commented Aug 5, 2023

So there's no reason we know of not to merge this? (We seem to be dragging our collective feet on it). (Though I already did the testing for tomorrow's release)

@cielf
Copy link
Collaborator

cielf commented Aug 8, 2023

Going ahead and merging it.

@cielf cielf merged commit 6468407 into rubyforgood:main Aug 8, 2023
11 checks passed
@awwaiid
Copy link
Collaborator

awwaiid commented Sep 10, 2023

Unfortunately this validates for all record saves, not limited to new partner applications. This caused issues with HE Banks that then couldn't edit Partner Agency Information without filling in the now-manditory fields (and surprised them). I think the intention was to only apply this validation of required fields during the initial application?

In any case, I'm going to hopefully-temporarily revert this so that the Banks are unblocked. I'll open a new issue to refresh this and maybe apply the rules only at the time of application (ex using AR validation context).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feat] Mandatory fields for submission of approval of profile information by partners
4 participants