Updated log and beers

Author: elektronikworkshop

BRANCHNOTES.md

@@ -92,6 +92,7 @@ During merging I found some bugs within those functions - mainly due to the abov
 **2020 02 20** Windows support - what a PITA. This OS is so foobar'ed... The only positive outcome from this experience: I found some substantial bugs in the parser which - of course (Murphy) - didn't affect me up to now. The parser should be much more resistant against strange paths and escapes now: Added proper command line lexer to cocopa and worked around several ridiculous Windows shortcomings (Microsoft owes me at least 50 crates of beer). The whole mess is not cleaned up and committed yet so please don't build from the repository and use the alpha release packages as outlined above.
 **2020 02 21** Discovered problems and bugs in the current official release from Microsoft: Fixed event handling within board manager. Added validity checks when loading board configurations from arduino.json. Better error handling and code locality, for details see commit.
 **2020 02 22** Worked on cocopa unit tests: restored broken tests and added platform test for built-in parser. Added path normalizing for include paths for both cocopa and vscode-arduino. Verified correct behaviour on Windows with latest release (alpha tester claimed it not to be working)
+**2020 02 23** Several tests, fixes and improvements within cocopa. `Arduino.h` now added to forced includes. Fixed code which wasn't linted up to now. Added hint to end of build how to rebuild the IntelliSense configuration. Added missing version field to `c_cpp_properties.json`.
 
 ## Status
 |      | Tasks   |
@@ -171,6 +172,7 @@ I will list every supporter here, thanks!
 2020-02-20 Elektronik Workshop: 56 :beers: (14h coding)
 2020-02-21 Elektronik Workshop: 48 :beers: (12h coding)
 2020-02-22 Elektronik Workshop: 44 :beers: (11h coding)
+2020-02-23 Elektronik Workshop: 20 :beers: (5h coding)
 
 <!-- https://github.com/StylishThemes/GitHub-Dark/wiki/Emoji -->
 
@@ -215,6 +217,7 @@ I will list every supporter here, thanks!
 * Non-IDE unit testing - to eliminate dependency injection use ts-mock-imports for instance
 * Hardcoded and scattered constants:
   * Load package.json and use values from therein instead of hard coding redundant values like shortcuts (like I did for the IntelliSense message in `arduino.ts`)
+  * Line splitting and other regexes
   * Scan code for other hard coded stuff and take appropriate countermeasures
 
 ## Non-categorized Notes