How should passing objects to normal elements be handled?

[justinbmeyer]

If a key:from="value" binding exists and value is an object, I think it should set the key property on the element.

For example, I think record should be available on the <div>:

import {stache} from "//unpkg.com/can@5/core.mjs";

const view = stache(`
  <div id="theDiv"
      record:from="this.record">
      This is a div
  </div>
`);

const fragment = view({
  record: {name: "I am some data"}
});

document.body.appendChild(fragment);

var theDiv = document.getElementById("theDiv");

console.log(theDiv.record)

https://codepen.io/justinbmeyer/pen/MzyXjG?editors=0011

I think this will help with custom elements. We can pass values directly to them.

This can deprecate domData. Also, it currently sets the record attribute to "[object Object]", so I don't think this will be a breaking change.

[chasenlehara]

Setting a property sounds right to me, but I’m not 100% sure.

Here’s an issue I filed about setting properties on custom elements: canjs/can-stache#278

[justinbmeyer]

Also, another thing to consider, if folks want to set attributes, they can use prop="{{value}}".

Here's what I think the rules should be:

• prop:from="key" - If on an element that does not have a viewModel, this should set a property.
• prop="{{value}}" - setAttribute

I like this because prop="{{value}}" makes it clear that value will be converted to a string.