Clarify a couple of pitfalls I landed in

[patricksurry]

Description

Non-functional doc changes that clarify a couple of pitfalls I fell into while learning mithril. Trying to use a class instance as a component rather than the class itself leads weirdness as mithril ends up using the object instance as a prototype for a new object with shadowed properties.

With single keyed fragments I missed the point about keying the child rather than the shared parent object and took a while to realize my mistake. Maybe there's a better explanation for why it's that wya.

Motivation and Context

Save time and simplify the learning curve.

How Has This Been Tested?

Doc.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation change

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• [] I have added tests to cover my changes.
• All new and existing tests passed.
• I have updated docs/changelog.md

[dead-claudia]

This line is not true. The oninit lifecycle method is still called. This is on rare occasion used with component subclasses, in particular in cases where a supertype needs to do things after the class is fully initialized.

class SuperClass {
    constructor(vnode) {
        // do things to set up superclass
    }

    oninit() {
        // maybe register an instance property or something
    }
}

class SubClass extends SuperClass {
    constructor(vnode) {
        // do things to set up subclass
    }
}

Also, please keep individual paragraphs on one code line to match the surrounding code style. Most editors automatically wrap Markdown, so that shouldn't be much of a problem.

[dead-claudia]

What exactly is the intent here? I'm not sure how this applies in or out of context. (Also, Latin abbreviations like "i.e." isn't as widely known among non-native speakers, so it's best to avoid those in general in the docs.)