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

[NFC] Date metadata fixes towards CRM-19490, CRM-18387, CRM-20012, CRM-20011, CRM-15948, CRM-19911 #9845

Merged
merged 3 commits into from
Feb 16, 2017

Conversation

eileenmcnaughton
Copy link
Contributor

@eileenmcnaughton eileenmcnaughton commented Feb 16, 2017

These commits are the NFC changes towards a bunch of date issues. Basically most of the problems go away once we swap custom handling for metadata-based date picker fields. Date picker fields use only ISO data format at the php level so a lot of non-robust custom data handling can go - & with it a bunch of problems.

This patch simply works to make the metadata available for the switch. I am trying to make the actual switch in a bunch of small changes in order to try to find any gotchas


Enhance the information available about dates. Based on the date format a format string in php and in 'our posix' should be returned.
(as long as we set the context to 'input' our of cautiousness. min & max year should be calculated for all types, not just credit cards
The importable fields function is not returning all possibly useful fields, it is filtering them by criteria that are
a bit unreliable. They are not being used here for filtering so we should get the full library in all cases.
…e profile fields.

This is further NFC change towards CRM-19840 and a range of other date fixes. It ensures that date data is available on date fields
allowing us to reduce code elsewhere
Copy link
Contributor

@seamuslee001 seamuslee001 left a comment

Choose a reason for hiding this comment

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

These all look ok and i think this has been tested before and not showing any issue

@eileenmcnaughton
Copy link
Contributor Author

Yes, all these have been in the larger PR we have been testing - it's just that I'm trying to figure out how to keep the change as safe as possible & hence trying to change the metadata first & then work through the flow-on field changes.

@seamuslee001
Copy link
Contributor

My feeling is that as long as this passes tests then i think its ok to move forward with.

@eileenmcnaughton eileenmcnaughton merged commit e9708ed into civicrm:master Feb 16, 2017
@eileenmcnaughton eileenmcnaughton deleted the cust_date_under branch February 16, 2017 04:59
@eileenmcnaughton
Copy link
Contributor Author

done!

monishdeb pushed a commit to monishdeb/civicrm-core that referenced this pull request May 2, 2017
[NFC] Date metadata fixes towards CRM-19490, CRM-18387, CRM-20012, CRM-20011, CRM-15948, CRM-19911
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