[REF][Import] add formatted parameter to formatInput #14986
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
(Standard links)
|
seamuslee001
approved these changes
Aug 7, 2019
|
unrelated fail |
eileenmcnaughton
added a commit
to eileenmcnaughton/civicrm-core
that referenced
this pull request
Aug 8, 2019
Unit test for civicrm#14986 along with some code comments in the test about issues I hit doing what I thought was the right fix - copied here for visibility // @todo I feel like we should work towards this actually parsing $params here - // & dropping formatting but // per civicrm#14986 for now $formatted is parsing // The issue I hit was that when I tried to extend to checking they were correctly imported // I was not actually sure what correct behaviour was for what dates were accepted since // it seems to ignore the latter in favour of the former - which seems wrong.
eileenmcnaughton
added a commit
to eileenmcnaughton/civicrm-core
that referenced
this pull request
Aug 8, 2019
Unit test for civicrm#14986 along with some code comments in the test about issues I hit doing what I thought was the right fix - copied here for visibility // @todo I feel like we should work towards this actually parsing $params here - // & dropping formatting but // per civicrm#14986 for now $formatted is parsing // The issue I hit was that when I tried to extend to checking they were correctly imported // I was not actually sure what correct behaviour was for what dates were accepted since // it seems to ignore the latter in favour of the former - which seems wrong.
|
tx @eileenmcnaughton ! |
magnolia61
pushed a commit
to magnolia61/civicrm-core
that referenced
this pull request
Oct 13, 2019
Unit test for civicrm#14986 along with some code comments in the test about issues I hit doing what I thought was the right fix - copied here for visibility // @todo I feel like we should work towards this actually parsing $params here - // & dropping formatting but // per civicrm#14986 for now $formatted is parsing // The issue I hit was that when I tried to extend to checking they were correctly imported // I was not actually sure what correct behaviour was for what dates were accepted since // it seems to ignore the latter in favour of the former - which seems wrong.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
fix an issue when importing contribution's custom field of type date
Before
Custom field of type date in csv file is not imported for Contributions, the value is removed after the formatting
After
Custom field of type date in csv file is imported
Technical Details
fix PR #13823
Comments
I don't really like this - but on digging in I feel like as an rc fix it's the safest. A better fix would have less confusing params being passed around - ie there is no obvious reason for $formatted rather than params to be populated here
@seamuslee001 I updated #14984 to have the test fix & target the rc