A few pieces were more complicated than others, but overall it wasn’t actually as complex as I once expected it to be. I had also been working on a skeleton for the parser, which I filled up with the new knowledge. Using those results, I learned the meaning of the most important flags, and a few fields that were not yet described in the tests’ structure.
![react event mac os command key react event mac os command key](https://www.switchingtomac.com/wp-content/uploads/2020/03/mac-keyboard_cmd-ctrl-power.jpg)
Thanks to Giannis’ extensive list of lines to test for, I managed to build a considerably comprehensive test suite, which I was able to use to figure out the workings of the SHExplorerParseCmdLine function.
![react event mac os command key react event mac os command key](https://miro.medium.com/max/1400/1*tNt-7LRHVjaX-tZXvhSbYQ.png)
It’s not like I coded all of that over the weekend though, I merely got back on track, finishing what I had been working over the past two weeks.
![react event mac os command key react event mac os command key](https://reactjs.org/static/bb4b10114882a50090b8ff61b3c4d0fd/31868/react_17_delegation.png)
Then I started refreshing my mind with what I was in the middle of doing, and by Sunday night I had the explorer command line parser working more or less as intended (it still has a few places where it doesn’t behave exactly like Windows’ parser, but it’s close enough for what we need). When I said last week’s report would be short, I was still planning to write a few lines about what I had been doing on the spare time from the university project, but by the time the weekend came I was way too mentally exhausted to actually do it.