Skip to content

Instantly share code, notes, and snippets.

@yyx990803
Created January 21, 2019 17:19
Show Gist options
  • Star 3 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save yyx990803/971e31b08b928c7886dde797291e59ec to your computer and use it in GitHub Desktop.
Save yyx990803/971e31b08b928c7886dde797291e59ec to your computer and use it in GitHub Desktop.
<SomeComponent>
<template #header>
<div>Header message</div>
</template>
<template #item="{ item }">
<div class="item">{{ item.text }}</div>
</template>
<template #footer>
<div>Footer message</div>
</template>
</SomeComponent>
@Lee182
Copy link

Lee182 commented Jan 21, 2019

My initial thoughts that it was object destructing and that all the key values in header would be binded as attribute property.
On seconds thoughs reading the purpose I think # clashes with css for id.

Maybe something like a ^ hat symbol be better because its pointing to something outside the component.

<SomeComponent>
  <template ^header>
    <div>Header message</div>
  </template>

  <template ^item="{ item }">
    <div class="item">{{ item.text }}</div>
  </template>

  <template ^footer>
    <div>Footer message</div>
  </template>
</SomeComponent>

@comfuture
Copy link

how about <template &foo>?
& symbol often used as meaning reference in other language. :)

@ChangJoo-Park
Copy link

how about <template &foo>?
& symbol often used as meaning reference in other language. :)

👍

@yyx990803
Copy link
Author

FYI - please don't discuss alternatives here, Gist doesn't have comment notifications and this is NOT the RFC itself.

Alternative symbols have been extensively discussed in the RFC threads and comments here are unlikely to be considered.

If you have strong opinions, participate in the discussions in the rfcs repo instead.

@nkostadinov
Copy link

Looks great , guessed it right away. The # is good because it is associated with id. this will be a great shorthand addition

@kahl-dev
Copy link

Awesome

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment