Timeline for Parsing and summarizing an aviation METAR (US) report
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 19, 2016 at 12:09 | history | edited | Yarh | CC BY-SA 3.0 | added 294 characters in body; edited title |
| Dec 19, 2016 at 11:52 | vote | accept | Yarh | ||
| Dec 16, 2016 at 11:52 | answer | added | Peter Taylor | timeline score: 1 | |
| Dec 15, 2016 at 23:18 | history | edited | 200_success | CC BY-SA 3.0 | deleted 66 characters in body; edited tags; edited title |
| Dec 15, 2016 at 23:04 | comment | added | Roland Illig | You should write unit tests until you reach 100% code coverage. Doing that you will notice that your code is buggy since it never reports "SN-". | |
| Dec 15, 2016 at 21:56 | answer | added | Christopher Wells | timeline score: 1 | |
| Dec 15, 2016 at 13:28 | answer | added | mtj | timeline score: 1 | |
| Dec 15, 2016 at 10:35 | comment | added | Yarh | @Peilonrayz thank you, I reverted edited code part | |
| Dec 15, 2016 at 10:31 | history | edited | Yarh | CC BY-SA 3.0 | added 369 characters in body |
| Dec 15, 2016 at 10:26 | history | rollback | Peilonrayz♦ | Rollback to Revision 1 | |
| Dec 15, 2016 at 10:26 | comment | added | Peilonrayz♦ | Please do not update the code in your question to incorporate feedback from answers, doing so goes against the Question + Answer style of Code Review. This is not a forum where you should keep the most updated version in your question. Please see what you may and may not do after receiving answers. | |
| Dec 15, 2016 at 10:17 | history | edited | Yarh | CC BY-SA 3.0 | deleted 46 characters in body |
| Dec 15, 2016 at 9:53 | answer | added | Mario Santini | timeline score: 1 | |
| Dec 15, 2016 at 9:10 | history | asked | Yarh | CC BY-SA 3.0 |