In my current use case, I have this (simplified) class hierarchy: List extends Control extends Widget and List also mixes in two Traits. The constructor of all these is identical with its definition: constructor (parent, config) and the config param is an object. Though not each key of the config param is parsed by the List class, some are by the Control and others by the Widget. If you look at the documentation for the List class, you might wanna see them all instead of inspecting each class itself and gather all keys for yourself. Thus it makes sense to tell the document tool, where it can find these additional config options.
In my current use case, I have this (simplified) class hierarchy:
List extends Control extends Widgetand List also mixes in two Traits. The constructor of all these is identical with its definition:constructor (parent, config)and the config param is an object. Though not each key of the config param is parsed by the List class, some are by the Control and others by the Widget. If you look at the documentation for the List class, you might wanna see them all instead of inspecting each class itself and gather all keys for yourself. Thus it makes sense to tell the document tool, where it can find these additional config options.