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] Add a note in documentation of CRM_Utils_Mail::send to clarify … #26803

Merged
merged 2 commits into from
Jul 13, 2023

Conversation

seamuslee001
Copy link
Contributor

…array keys are case specific and replace some CRM_Utils_Array::value

Overview

This adds a note to clarify that the array_keys of the params are case specific and replace some CRM_Utils_Array

Before

Documentation isn't that clear that the keys are case specific

After

Documentation is clearer and deprecated code style removed

ping @colemanw @demeritcowboy

…array keys are case specific and replace some CRM_Utils_Array::value
@civibot
Copy link

civibot bot commented Jul 13, 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 13, 2023
CRM/Utils/Mail.php Outdated Show resolved Hide resolved
@@ -223,10 +224,10 @@ public static function send(array &$params): bool {
$headers['Content-Type'] = $htmlMessage ? 'multipart/mixed; charset=utf-8' : 'text/plain; charset=utf-8';
$headers['Content-Disposition'] = 'inline';
$headers['Content-Transfer-Encoding'] = '8bit';
$headers['Return-Path'] = CRM_Utils_Array::value('returnPath', $params, $defaultReturnPath);
$headers['Return-Path'] = $params['returnPath'] ?? $defaultReturnPath;
Copy link
Contributor

Choose a reason for hiding this comment

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

When there's a 3rd param it's not always a 1-1 swap so just need to consciously think about null (philosophy question: Is it physically possible to think about nothing?). This case is ok, and probably more like what was actually intended originally, e.g. before null would result in null, whereas now it's more like you might expect:

$params['returnPath'] = NULL;
var_dump(CRM_Utils_Array::value('returnPath', $params, '[email protected]'));
var_dump($params['returnPath'] ?? '[email protected]');

outputs:

NULL
string(20) "[email protected]"

@demeritcowboy demeritcowboy merged commit fc0a25d into civicrm:master Jul 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants