Skip to content

Rendering a promise is broken when rendering other values after #2

Description

@ruphin

There are some bugs with rendering Promises.

If a NodePart renders a Promise, then another value (any other), and then the first Promise again, it will not do anything when it resolves. I'm also fairly certain that other scenarios with Promises are broken, and it needs a more robust implementation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions