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

[REF] ScheduleReminders - Cleanup "sublimely stupid" form code #26876

Merged
merged 1 commit into from
Jul 19, 2023

Conversation

colemanw
Copy link
Member

Overview

Initial cleanup of the ScheduleReminders form... toward sanity.
Lots more refactoring to do, this fixes the easy-to-fix things that were obviously wrong.

Lots more refactoring to do, this fixes the easy-to-fix things that were obviously wrong.
@civibot
Copy link

civibot bot commented Jul 19, 2023

Thank you for contributing to CiviCRM! ❤️ We will need to test and review the PR. 👷

Introduction for new contributors
  • If this is your first PR, an admin will greenlight automated testing with the command ok to test or add to whitelist.
  • A series of tests will automatically run. You can see the results at the bottom of this page (if there are any problems, it will include a link to see what went wrong).
  • A demo site will be built where anyone can try out a version of CiviCRM that includes your changes.
  • If this process needs to be repeated, an admin will issue the command test this please to rerun tests and build a new demo site.
  • Before this PR can be merged, it needs to be reviewed. Please keep in mind that reviewers are volunteers, and their response time can vary from a few hours to a few weeks depending on their availability and their knowledge of this particular part of CiviCRM.
  • A great way to speed up this process is to "trade reviews" with someone - find an open PR that you feel able to review, and leave a comment like "I'm reviewing this now, could you please review mine?" (include a link to yours). You don't have to wait for a response to get started (and you don't have to stop at one!) the more you review, the faster this process goes for everyone 😄
  • To ensure that you are credited properly in the final release notes, please add yourself to contributor-key.yml
  • For more information about contributing, see CONTRIBUTING.md.
Quick links for reviewers

@civibot civibot bot added the master label Jul 19, 2023
@@ -138,17 +146,12 @@ public function buildQuickForm(): void {
}
}
else {
// Dig deeper - this code is sublimely stupid.
Copy link
Member Author

Choose a reason for hiding this comment

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

This is easily my favorite comment in our codebase. I'm sorry to see it go @totten

Copy link
Member

Choose a reason for hiding this comment

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

Well, I guess that code had to wander 7 years through the wilderness, but now... it's sublimely smart... I hope...

@colemanw colemanw changed the title ScheduleReminders - Cleanup "sublimely stupid" form code [REF] ScheduleReminders - Cleanup "sublimely stupid" form code Jul 19, 2023
@seamuslee001
Copy link
Contributor

Jenkins re test this please

@colemanw
Copy link
Member Author

@seamuslee001 was that just a drive-by comment or were you gonna merge this?

@seamuslee001
Copy link
Contributor

ok this seems ok

@seamuslee001 seamuslee001 merged commit 5c7fb32 into civicrm:master Jul 19, 2023
@seamuslee001 seamuslee001 deleted the scheduleReminderForm branch July 19, 2023 22:55
@totten
Copy link
Member

totten commented Jul 19, 2023

I played around with it a bit on the test site -- it exhibited consistency in writing/reading the "Entity"-related options. So that seems good.

My process was to make one "Scheduled Reminder", then repeatedly edit it (changing the "Entity" to some random values). There were a few PHP warnings. I haven't tested carefully enough to see if they originate here.

Screen Shot 2023-07-19 at 4 01 46 PM Screen Shot 2023-07-19 at 4 01 54 PM

@colemanw
Copy link
Member Author

@totten yea, that's because the form has to do its own deserialization of the values from BAO::retrieve because that function sucks. I'll get to that...

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

Successfully merging this pull request may close these issues.

3 participants