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

FIX | TestMailer uses new testsession APIs for handling state #188

Conversation

dnsl48
Copy link

@dnsl48 dnsl48 commented May 17, 2019

This PR is a follow up on silverstripe/silverstripe-testsession#65

@@ -94,6 +94,6 @@ protected function saveEmail($data)
$state->emails = array();
}
$state->emails[] = array_filter($data);
$this->testSessionEnvironment->applyState($state);
$this->testSessionEnvironment->saveState($state);

Choose a reason for hiding this comment

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

The change looks OK. The doc blocks aren't particularly useful and I'm not familiar with the difference, but presumably this has been tested in behat and fixes a problem, so LGTM

@robbieaverill
Copy link

Would you mind fixing the builds to ensure they're still green?

This branch is for SilverStripe 5.x, so you may want to retarget the PR. The Travis config needs recipe constraints changed from 2.x to 5.x

@dnsl48
Copy link
Author

dnsl48 commented Jun 13, 2019

sure, will do, thank you for taking a look :)

@GuySartorelli
Copy link
Member

@dnsl48 Do you know what specifically this was solving? Was there a bug that this fixes? I'm inclined to close this PR given we've been running behat tests for 4+ years since the PR was opened and this hasn't seemed to be a problem.

@dnsl48
Copy link
Author

dnsl48 commented Dec 14, 2023

Hey @GuySartorelli, sorry, I don't remember the exact details.
Looks like everything is okay as is without this patch :)

@dnsl48 dnsl48 closed this Dec 14, 2023
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