Closed peterdesmet closed 11 years ago
Yes, this file (dateFormat.txt) is used in automated tests, so no need to load them in the UI.
Concerning the dubious dates : according to the current definition of the processor we "only produce results from data that are without uncertainty." So returning nothing for those date is what is expected, even if I agree that the year alone could be useful in some cases. This would require additional design to include support for all dates like 2012-12-32 where only a portion is valid.
You should also create branches on your forked repo, not on Canadensys and send the Pull Request from there (forked repo).
So, you could enter a new issue to support partially valid dates if you want.
Ok!
nice!, thanks Peter Keeping track of the original repo : http://bassistance.de/2010/06/25/git-fu-updating-your-github-fork/
2 changes to the
dateFormat.txt
file, one of which requires more implementation.And a question:
The test files
dateFormat.txt
andDDMMSSCoordinatesFormat.txt
are currently;
separated files. Are these used in automated tests? Because, it would be nice if the file could also be tested directly in the web interface. Something like:The first column will be interpreted as an ID, and can be used for visual checking, the second column is the date that is parsed.
You can remove the branch
dateFormat
if you no longer need it.