Conversation
trying out yamale though
- added date validator - included time-machine and bugzoo fields in sample bug
not the best solution, since difficult to generalize URLs
trying out yamale though
- added date validator - included time-machine and bugzoo fields in sample bug
not the best solution, since difficult to generalize URLs
| languages: | ||
| - CMake | ||
| time: 2014-11-21 (12:57) | ||
| time: 2014-11-21T12:57:00Z |
There was a problem hiding this comment.
Please note again: unless the original time was already in UTC, this is not a valid conversion.
It's likely these times were reported in CET or CEST, which would make this +0200 (but this is just a guess).
There was a problem hiding this comment.
I have not worked on that. As I mentioned in the comment, I have worked only on fault and failure codes.
There was a problem hiding this comment.
I'm not sure I understand your comment: are you saying you didn't change these time entries?
What makes them show up in the diff here?
There was a problem hiding this comment.
Does this PR build on #359? See also #359 (comment), where I commented on 0c46707.
There was a problem hiding this comment.
Yes this PR is behind #359. I have not modified the time yet after your comment.
I have not worked on that.
Sorry about the confusion. I meant 'after your comment'.
There was a problem hiding this comment.
To prevent we accidentally merge this, perhaps drop 0c46707 for now?
| languages: C++ | ||
|
|
||
| time: 2015-03-03 (2015-03-12 2:53 GMT+1) | ||
| time: 2015-03-03T2015-03-12:00Z 2:53 GMT+1 |
| languages: C++ | ||
|
|
||
| time: 2014-05-12 (21:11 GMT+1) | ||
| time: 2014-05-12T21:11:00Z GMT+1 |
| languages: CMake | ||
|
|
||
| time: 2014-12-16 (10:01am GMT+1) | ||
| time: 2014-12-16T10:01am:00Z GMT+1 |
|
closing for #391 |
3 participants
Currently added only fault and failure codes. This PR is behind #359