More complex example? about svelte-meteor-data

[rdb]

Hi, sorry to not have noticed this issue earlier. Before I look closer at your use case, I have just a question, do you have the immutable flag set in svelte:options?

[skandragon]

I do not have that flag set. With Meteor, I'm not even sure how to set it.

That said, I seem to have solved my problems. Mostly. Kinda. :)

The work-around / solution is to make sure that I always refer to $planet in some way. For example,

function foo() {
  return planet.name
}

If I call this function as {foo()} it will return what feels like a random name for a random planet. If I rewrite this to pass in the $planet it works properly.

[rdb]

I think if you were to use destructuring syntax or accessed it via its properties it would work:

{#each $planets as planet}<Planet {...planet}/>{/each}

or

{#each $planets as planet}<Planet name={planet.name}/>{/each}

The way I recommend doing it is to just pass in the identifier:

<script>
$: planets = Planets.find({}, {fields: {_id: 1}});
</script>
{#each $planets as planet (planet._id)}<Planet id={planet._id}/>{/each}

And then in the Planet component, do something like this:

export let id;
$: planet = useTracker(() => Planets.findOne(id));

That makes sure that you have a reactive $planet store available in the Planet component that does update when its properties change.

[skandragon]

Sounds good, thanks!