This is a continuation of issue #362 separated for can-define/list/list. It was separated to provide amiable and more accurate estimates.
discussion:
The events subsection and prototype subsection have different route styles. It would be good to keep one style across documentation. This seems to stem from a difference of how documentation is being produced. The prototype methods have their documentation written in the main list.js file.
can-define/list/list/AddEvent.html
vs:
can-define/list/list.prototype.assign.html
Would it be prudent to compare related functions to either MDN or variants like assignDeep on Map and List?
Pop has a See Also section, should this be implemented as a standard?
This is a continuation of issue #362 separated for can-define/list/list. It was separated to provide amiable and more accurate estimates.
can-define/list/list
{can-define/list/list}in the Returns subheading on new DefineList([items]) linking to the page it's currently on.can-define/list/list/AddEvent.html
can-define/list/list/LengthEvent.html
can-define/list/list/PropertyNameEvent.html
can-define/list/list/RemoveEvent.html
can-define/list/list.prototype.assign.html
can-define/list/list.prototype.assignDeep.html
can-define/list/list.prototype.concat.html
can-define/list/list.prototype.every.html
can-define/list/list.prototype.filter.html
can-define/list/list.prototype.forEach.html
can-define/list/list.prototype.get.html
can-define/list/list.prototype.indexOf.html
can-define/list/list.prototype.join.html
can-define/list/list.prototype.lastIndexOf.html
can-define/list/list.prototype.map.html
can-define/list/list.prototype.pop.html
can-define/list/list.prototype.push.html
can-define/list/list.prototype.reduce.html
can-define/list/list.prototype.reduceRight.html
reduce.)can-define/list/list.prototype.replace.html
can-define/list/list.prototype.reverse.html
can-define/list/list.prototype.serialize.html
can-define/list/list.prototype.set.html
can-define/list/list.prototype.shift.html
can-define/list/list.prototype.slice.html
can-define/list/list.prototype.some.html
can-define/list/list.prototype.sort.html
can-define/list/list.prototype.splice.html
can-define/list/list.prototype.unshift.html
can-define/list/list.prototype.update.html
can-define/list/list.prototype.updateDeep.html
can-define/list/list.prototype.wildcard.html
can-define/list/list.prototype.wildcardItems.html
can-define/list/list.extend.html
discussion:
The events subsection and prototype subsection have different route styles. It would be good to keep one style across documentation. This seems to stem from a difference of how documentation is being produced. The
prototypemethods have their documentation written in the main list.js file.Would it be prudent to compare related functions to either MDN or variants like assignDeep on Map and List?
Pop has a See Also section, should this be implemented as a standard?
addedandremoveDocumentaddedandremove#403