Why we have to declare what are the attributes of the components? Can't we just use whatever the user writes as attribute automatically?

because then we have to blacklist native attributes depending on the element type, which can be cumbersome. A whitelist approach is explicit and safer.

I think 'dataAttributes' is a bit misleading, potential confusion with the datatset api ?

Perhaps 'bindAttributes' ?

For example, this seems odd,

<component data-qty="2"></component>

dataAttributes: ['data-qty']

Whereas,

bindAttributes: ['data-qty'],
ready : function(){ 
  console.log( this.qty );
}

We'd need to rename the binding key in this instance as well, this['data-qty'], seems messy.

data-qty="2"
\\--
this.qty === 2

yes, but bindAttributes also sounds misleading because we are not really binding it, its just a starting value.

Maybe paramAttributes?

elementAttributes, htmlAttributes, tagAttributes, domAttributes, attributes

+1 for paramAttributes
On Feb 22, 2014 8:29 AM, "Pierre Bertet" notifications@github.com wrote:

elementAttributes, htmlAttributes, tagAttributes, domAttributes,
attributes

Reply to this email directly or view it on GitHubhttps://github.com/yyx990803/vue/issues/125#issuecomment-35802549
.

Ah, mis-thought the whole binding part. Initial data, I follow now!

Absolutely, paramAttributes sounds perfect for what you describe.

how about the dead simple attr ?

@marfalkov there is already an attributes option which is a hash of attribute key/values to be added to the element.

So this is the exact opposite. Maybe the names could reflect that, with something like setAttributes and getAttributes?

setAttributes and getAttributes sounds good

I don't think they are logical counterparts - attributes is part of the element options while paramAttributes is a component configuration option.

@yyx990803 that makes sense.