Closed BobHarper1 closed 6 years ago
Cheers, we'll put the merge on the long finger.
For clarity, I've now changed this so that it will be an integer (which makes more sense when we're talking about months) and removes any ambiguity (cc @stevieflow)
@BobHarper1 -- @morchickit thinks it might be better to have this a positive number, to flag up to people who publish -7
months, for example (which is happening)...
Also - @Bjwebb can we have dev version of CoVE for this branch?
cc/ @KDuerden
We also discussed that it should be a float, not an integer. So this need to be a positive float (that can include zeros).
Agree on positive (set min to 0).
Does a float make sense to months? What is 0.5 of "a month"? For February, it's 14 days, for March 15.5...
Here's a CoVE deploy for this dev branch http://branch-360-186-duration-number.cove-360-dev.default.threesixtygiving.uk0.bigv.io/
We should now merge this @Bjwebb
A bug fix as discussed on the Forum https://forum.threesixtygiving.org/t/planned-dates-duration-months-field/188