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

Refactor out for_families attribute from FamilyRequestCreateService #4861

Conversation

coalest
Copy link
Collaborator

@coalest coalest commented Dec 16, 2024

Doesn't resolve any issue.

Description

This for_families attribute is a funny one. I removed it from RequestCreateService in PR #4827, because it was being passed in but then not used.

Let's go ahead and remove it from FamilyCreateService as I think it isn't necessary there either.

It also appears to be a column on the partner_requests table which as far as I can tell is currently not being used. Not sure if it was ever used.

A side topic is what to do about the partner_requests table. Can we drop it or does it have records in production?

Type of change

  • Internal refactor

How Has This Been Tested?

Fixed related tests that references for_families.

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.

I like it!

@dorner dorner merged commit 75af9ad into rubyforgood:main Dec 18, 2024
11 checks passed
@cielf
Copy link
Collaborator

cielf commented Dec 18, 2024

FYI, I've added whether partner requests can be deleted to our planning meeting list (but it's not near the top)

Copy link
Contributor

@coalest: Your PR Refactor out for_families attribute from FamilyRequestCreateService is part of today's Human Essentials production release: 2024.12.22.
Thank you very much for your contribution!

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.

3 participants