Skip to content

[Bug]: useSuspendingMyNode resolves Suspense with empty object cast to NodeInfo #1271

Description

@danditomaso

apps/web/src/components/PageComponents/Messages/MessageItem.tsx:34-52 implements a Suspense polling loop that calls resolve({} as Protobuf.Mesh.NodeInfo) every 100ms as a re-suspend trick.

The empty-object cast is a type lie — any downstream read like myNode.num sees undefined and can propagate silently. It also relies on Suspense retry behavior that isn't guaranteed. Replace with a signal-backed hook or a proper Promise that resolves once myNode is available.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions