[
https://issues.apache.org/jira/browse/CB-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269832#comment-13269832
]
Filip Maj commented on CB-565:
------------------------------
I suppose Plugin development is a use case (the {{extend}} method is available
in the {{cordova/utils}} JS module, so plugin authors _could_ use it if they
wanted to) but it simply applies to our core APIs.
Not so much an issue as just a point I want to bring up. With us taking a hard
look at how our docs are structured, perhaps these cases of extension should go
into the re-thinking of how our docs should be laid out. Maybe a Java-like doc
reference, with a hierarchy, makes sense? Maybe not...
Do you see value in communicating to our users, "Hey, this object actually
EXTENDS from this object." ?
> Somehow document how certain objects extend from others in cordova-js
> ---------------------------------------------------------------------
>
> Key: CB-565
> URL: https://issues.apache.org/jira/browse/CB-565
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Docs
> Affects Versions: 1.6.1
> Reporter: Filip Maj
> Assignee: Michael Brooks
>
> Certain objects available to cordova users extend from properties of other
> objects. In particular:
> * FileEntry and DirectoryEntry extends Entry
> * MediaFile extends File
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
