spek | A specification framework for Kotlin | Functional Testing library

webm is a media container similar to mkv, opus is a audio format which can be included in the webm among with video, other audio tracks and subtitles etc..

opus seems to have higher bitrate (better quality) than offered by youtube-dl/newpipe but not so great hardware support, that does not matter for your pc and phone though.

youtube does not offer uncompressed audio/video

When using mvnrepository.com, take note of which repository the module is available in as you only have JCenter configured for your build (which is usually fine, just not in this case). Here the dependency is in the Confluent repository:

So you will need to add this repository to your build:

The compiler doesn't tell you the member is not initialized, it's telling you that you are not allowed to call functions in the class body without them being part of a member declaration.

e.g.

You're looking for

The main issue is because you've attached the event handler to the textarea yet the visible element that's being typed in to is a contenteditable div. As such you need to correct your selector. As this element is a div you need to use text() or html() to read its content, not val(). It would also make more sense to use the input event for this.

Secondly, you need to fix the selector which targets the element to display the character count in.

You need to add an exclusion on one of the imports so it only adds the package once.

Example:

Memoization is remembering (caching) the result of a function call with a given set of parameter values so that if that same function is called again with the same parameter values, the cached result will be returned rather than having to re-run the function. It's an optimisation technique.

See more info here: https://en.wikipedia.org/wiki/Memoization

So in the example above Spek wraps the call to construct a Calculator in its memoized function, meaning that it will only construct it once, and thereafter calls to calculator will re-use that existing instance. And in terms of how you'd generally use it in a test, that would give you the same behaviour as constructing a new Calculator in beforeEachTest, but in a more concise way.