Inconsistent implementation of custom tags about marko HOT 3 CLOSED

The HTML syntax does not allow attribute types to be distinguished (similar to JSON). This is unfortunate, but short of introducing a new language we must live with a separate schema that informs the compiler of the types of each attribute. Alternatively, we would assume that every attribute is a string and for $/${ } to change the type (more typing and ugly).

Therefore, in your example, you would just need to do the following:

{
    "attributes": {
        "viewModel": "expression",
        "options": "expression"
    }
}

If we were willing to depart from an HTML parser, we could create our own HTML-like parser that supports the following:

<my-component number=1/>
<my-component expression=(a + b)/>
<my-component string="hello"/>
<my-component boolean=true/>

If we were to go that route then we would lose syntax highlighting/completion/validation support from existing HTML editors and tools like Emmet.

from marko.

Closing issue as I don't think there are any short-term actionable items. If you disagree please feel free to add comments.

from marko.

Hey @pedramphp, please provide comments on the following proposal: #90

from marko.