lucy | Lucy on Rails - Lucy in the sky with rubies

If you want to ignore first line while reading the CSV file then you can simple skip processing of 1st line by calling in.readLine(); twice at the start as shown in below example:

You can use len() which returns the number of elements in an object. This works on all iterables.

Use GroupBy.transform with join:

Not really sure what you mean by having three separate lists but check this example where I uses a Map> to split your dates into its own list:

So this is my attempt.

The development process here was to code by intention. That is, I started at the top level and called a function that I had not yet written. This was the line:

Based on your code I am assuming that each sentence is on a separate line. There are a couple of things in your code that are problematic. First, a matter of style: setting up a unit test is usually done in setUp, not in __init__.
Second, test_reader is not a test, but part of the setup, or can be done in the test itself. Tests that depend on each other is bad practice, also test functions that don't test anything.

Your test does not work, because test_reader is executed after test_capitalization -- unittest orders tests alphabetically by default.

So, here is an example for a working version, provided you have one sentence per line as assumed in your code:

You're looking for Typescript's Index Signature.

Assigning to super.prop is useful when prop is defined on the parent's prototype, not when it is defined as an instance property, as is the case with name in your code. Realise that the assignment name = 'jack' happens on the instance that is created by new b, not on some other object.

So when you do super.name = 'Lucy', you are doing nothing else than this.name = 'Lucy'. This change is not visible when you consult super.name after that assignment, because that will scan the parent's prototype chain, not the instance object. And there is no name defined anywhere on that prototype chain...

The difference between how super.name acts when used for lookup and for assignment is specific: for (non-setter) assignment, it is no different than assigning on this, while for lookup (including setter lookup), it skips this and starts the lookup in the parent's prototype chain.

The power of the super.prop syntax only reveals itself when you have to deal with methods that have been created on the prototype.

To demonstrate this, let's define name as a getter/setter function on the prototype:

You can use OPENJSON to break out the array into separate rows: