Conditional rendering example about simulacra

[gr0uch]

The template would contain both the list and the empty view. In your case, the template might look like:

<div class="items">
  <span class="empty-message"></span>
  <div class="item">
    <h5 class="name"></h5>
    <p class="description"></p>
  </div>
</div>

Then the state might look like:

{
  list: [ ... ],
  isEmpty: null
}

Here's an example of empty/error message in a template: https://github.com/fortunejs/fortune-http/blob/5ee54675e82cebf08b05029b706fa19da2627361/lib/template.html#L116-L117

[OEvgeny]

@daliwali Looks interesting. As I understood it means that we have to duplicate some UI related state fields and keep them in sync with existing data.
So, to update list in this particular case we need to do something like:

state.list.push(...items)
state.isEmpty = state.list.length === 0

Could we use sort of computed property to handle isEmpty state? E.g.

const state = {
  list: [],
  get isEmpty () { return this.list.length }
}

I tried this approach but it won't work (see this fiddle). Looks like es6 getters are ignored.
I tried to use Object.defineProperty instead, but this doesn't work for me too.

As I understand the problem is what we have to mutate values directly instead of compute them using getters. It should notify renderer about update. For Array it means that to react on update, we need a way to subscribe on its changes (or modify mutation methods) to be able to perform update of isEmpty state.

[gr0uch]

I understand what you mean. The simplest and easiest way to do this is to set it via the change function:

function (node, value, previous, path) {
  var target = path.target // reference to current object
  target.isEmpty = !target.list.length
}

This way you don't have to remember to set isEmpty manually. It can still be set manually from outside of the change function, though.

[OEvgeny]

Also there are some cases when keeping both branches of conditional could be problematic. For example when we have two different views of some data and need to switch between them. E.g. list view and cards view. This views can be different in terms of semantics and accessibility.

Is there any way to remove falsy conditional branches from current DOM?

[OEvgeny]

@daliwali

via the change function

Wow. I thought about something like that. But wasn't sure what it could be so simple :) Thanks!

[gr0uch]

E.g. list view and cards view. This views can be different in terms of semantics and accessibility.

In this case, you might need to set isEmpty for both views, this can be extracted into a helper function to be reusable.

Is there any way to remove falsy conditional branches from current DOM?

No, there is not. Even with a template language like Mustache, falsy branches are still in the template.

[OEvgeny]

E.g. list view and cards view.

I was thinking about something like:

const state = {
  currentView: 'list',
  items: [...]
}

In state. And template which looks like:

<div class="button-toggler">
   <!-- toggle views between card and list markup goes here -->
</div>
<div class="list-view">
   <div class="item">
     <!-- list item markup goes here -->
   </div>
</div>
<div class="card-view">
   <div class="item">
     <!-- card item markup goes here -->
   </div>
</div>

Sorry that it wasn't so clear from the previous message.

Now I understood what this will not work because we couldn't use one array for binding to multiple DOM nodes. To toggle between views we could use something like this in state:

const state = {
  currentView: 'list',
  cards: null,
  list: [...] // list will be shown
}

To toggle views we simply need to assign items to state.cards instead of state.list and flush the other one.

I wonder, is there a better way to handle such cases?

[gr0uch]

Why not just include all of the data in your list, and conditionally hide and show things in CSS? I'm not sure why its necessary to do this in JS at all.

[OEvgeny]

@daliwali as mentioned before markup could be different especially when semantics and accessibility involved. So, we couldn't just hide or show parts of markup because markup for each data representation (list item and card in this case) could be definitely different.

[OEvgeny]

Ah, I see another solution for this. We can simplify markup to something like:

<div class="button-toggler">
   <!-- toggle views between card and list markup goes here -->
</div>
<div class="view">
   <div class="item">
     <div class="list-view">
       <!-- list item markup goes here -->
     </div>
     <div class="card-view">
       <!-- card item markup goes here -->
     </div>
  </div>
</div>

And add classes to .view according to currentView state to indicate which data representation should be shown. But if we need to map same item fields to both representations it won't work.

[gr0uch]

In your case, I guess having two different lists is unavoidable.

You could do something very similar to the example I gave before and modify the second list via the first list's change function:

function (node, value, previous, path) {
  var target = path.target
  target.cards = target.list.slice()
}

[OEvgeny]

@daliwali Got it. Thank you.

And thanks for sharing simulacra! Keep doing good stuff :)