This is a continuation of issue #362 separated for can-define/map/map. It was separated to provide amiable and more accurate estimates.
Needs:
Discourse:
Needs:
Discourse:
Needs:
Discourse:
- Does this need a use section? The boolean section seems fairly descriptive.
Needs:
Discourse:
- Article is a stub, and doesn't include a Use section.
map.assign(props) is fairly descriptive.
Needs:
Needs:
Discourse:
Needs:
Discourse:
Needs:
Discourse:
- map.get(propName) should probably have an example that doesn't include undefined. Might be good to have a verbose example for get and in comparison of how it returns values.
const todo = new DefineMap({ name: 'example', complete: false });
console.log(todo['name'] === todo.get('name')); // true
Needs:
Discourse:
Needs:
Discourse:
.get(propName) only should be used when reading properties that might not have been defined yet, but will be later via [can-define/map/map.prototype.set].
Needs:
Needs:
Needs:
Discourse:
- It might be worth it to have a verbose use section for all wildcard.
This is a continuation of issue #362 separated for can-define/map/map. It was separated to provide amiable and more accurate estimates.
can-define/map/map.html
map/KeysEvent.html
Needs:
Discourse:
map/PropertyNameEvent.html
Needs:
map/map.extend.html
"can"importDiscourse:
map/map.seal.html
Needs:
Discourse:
map/map.prototype.assign.html
Needs:
Discourse:
map.assign(props)is fairly descriptive.map/map.prototype.assignDeep.html
Needs:
["first", "2", "3"].map/map.prototype.deleteKey.html
Needs:
Discourse:
map/map.prototype.forEach.html
Needs:
Discourse:
map/map.prototype.get.html
Needs:
Discourse:
map/map.prototype.serialize.html
Needs:
Discourse:
map/map.prototype.set.html
Needs:
Discourse:
map/map.prototype.update.html
Needs:
map/map.prototype.updateDeep.html
Needs:
map/map.prototype.wildcard.html
Needs:
Discourse: