Skip to content

Expose Pinia Colada signals in loaders #605

Open
@posva

Description

@posva

Currently the signal exposed in query in colada loaders is the one from loaders, tied to the navigation. But in queries, there is another signal related to the query itself.

Merging both signals

We could merge both signals with AbortSignal.any() (newly available so will need a polyfill). This would be partly breaking but seems to be the most intuitive version

Adding both signals individually

We could merge both signals into signal: { navigation, query } and let users merge

Adding a new property to loaders

signals (plural) so the signal is kept

Metadata

Metadata

Assignees

No one assigned

    Labels

    ⚡️ enhancementimprovement over an existing feature

    Projects

    Status

    📋 Backlog

    Status

    🆕 Triaging

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions