-
-
Notifications
You must be signed in to change notification settings - Fork 825
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
Upgrade When package to the lastest version #15223
Conversation
(Standard links)
|
de607b4
to
cbe9baa
Compare
cbe9baa
to
9dbd706
Compare
fail relates |
@seamuslee001 thanks and thanks for adding the Agileware ref! Legend! |
@jusfreeman i'm not sure how to fix the test failures but given that Pengyi has looked into it already maybe he can give some guidance here |
9dbd706
to
d682bf2
Compare
@seamuslee001 we won't be able to get to this one today, however should have time next week. It's on our board to action. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed the fails.
Should I submit a new PR against this branch or the master branch?
I have made the changes in this commit |
Thanks @agileware-pengyi i have brought that commit in, i will need another reviewer to review this now @eileenmcnaughton @monishdeb |
@seamuslee001 I think this is mergeable it you and @agileware-pengyi have reached agreement - without having gone into the code to the level you two have nothing jumps out as concerning |
@seamuslee001 thanks |
@eileenmcnaughton @agileware-pengyi i have also just pushed one minor change which is setting the ignoring of exceptions to only happen when in UnitTests UF because i figure we still want Execptions to be thrown so they show up as status messages |
That makes sense to me. Just noting that this exception with message |
Working on exclude dates issue. It needs some changes for the new version. |
Following the old way to generate the occurrences. see agileware@410b858 More confidence with this one because of fewer changes. One thing I notice is that civicrm-core/CRM/Core/BAO/RecurringEntity.php Line 992 in e058b26
civicrm-core/CRM/Core/BAO/RecurringEntity.php Line 1018 in e058b26
|
@seamuslee001 ping just in case you missed it |
Awesome. And after merging this PR we need to remove the When package thus there should be a followup PR that removes it from packages/* |
e058b26
to
d4424ef
Compare
thanks @agileware-pengyi incorporated now |
@monishdeb packages PR is here civicrm/civicrm-packages#264 |
Ug - needs a rebase |
Update composer.lock to match the commits's composer.json
d4424ef
to
30aa3e5
Compare
rebased now @eileenmcnaughton |
Merging so we get plenty of testing during the 5.20 release cycle. @seamuslee001 Do we need a PR to remove from packages? |
Overview
This picks up the work from @agileware-pengyi in #14903 and goes for more of a straight composer way with this PR. Note that this PR is expected to fail testing
Note to @agh1 please make sure @agileware-pengyi is credited
Before
Old version of When package is used
After
Newer version of When package used
In terms of tests i am expecting that CRM/Core/BAO/RecurringEntityTest is going to fail as it is locally which suggests we do have some unit tests already covering this code
ping @jusfreeman @eileenmcnaughton
Agileware ref: CIVICRM-1223