fix: deep nested preact signals in props

[ph1p]

Changes

This extends my work from: #11834 (review)
Now its possible to nest the signals.

If you have this:

---
const count = signal(10);

const dataObj = {
  count,
  deep: {
    signal: count,
    ok: [signal(1), signal(423), 'string'],
    evenDeeper: {
        signal: signal(0),
    },
  },
};

const dataArr = [signal(401), dataObj];
---
<ArrObjSignal dataArr={dataArr} dataObj={dataObj} client:load />

Now the preact signal structure looks like this:

{
  "dataObj":{
    "count":"p1",
    "deep.signal":"p1",
    "deep.ok.0":"p2",
    "deep.ok.1":"p3",
    "deep.evenDeeper.signal":"p4"
  },
  "dataArr": {
    "0":"p0",
    "1.count":"p1",
    "1.deep.signal":"p1",
    "1.deep.ok.0":"p2",
    "1.deep.ok.1":"p3",
    "1.deep.evenDeeper.signal":"p4"
  }
}

Testing

Included.

Docs

nothing should change for the user.

[changeset-bot]

🦋 Changeset detected

Latest commit: db7ae4d

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[ematipico]

Tests are failing

[ph1p]

Ok, I looked at the tests and “Lit components” sometimes fails and sometimes doesn't. This has nothing to do with this change. I also jumped to the current state of the main and there it also happens from time to time.

[matthewp]

Yeah I'm sure that's unrelated here.

[matthewp]

@ph1p would you mind resolving conflicts?

[ph1p]

Sure! But I'm currently on vacation. I'll do it on Saturday if it's ok :)

[ematipico]

@ph1p it seems that your changes are caused some regressions in our e2e tests. Could you please look after them?

[florian-lefebvre]

@ph1p are you still interested in this PR?

[ph1p]

Yes very much @florian-lefebvre
Sorry, was a bit busy

[florian-lefebvre]

No problem, just wanted to check. Let us know if you need help