wasvy-org/wasvy

`QueryResolver` should contain (wrap) `queries`

Open

#39 opened on Jan 22, 2026

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (6 forks)auto 404
good first issue

Repository metrics

Stars
 (126 stars)
PR merge metrics
 (PR metrics pending)

Description

Wasvy's dynamic systems make use of a single ParamSet to retrieve queries. Since a ParamSet is accessed by index, the QueryResolver struct exists in Wasvy to facilitate WasmQuery (and other system params in the future) accessing the correct index that corresponds with their query.

Currently when running a system, both a reference to the ParamSet and a QueryResolver are passed separately to the WasmHost (see dynamic_system in system.rs).

Ideally the QueryResolver completely wraps and holds the mutable reference to the queries, so accessing them can only be done through its own interface.

Blocked by: #38

Contributor guide

Research direction
Understand how ParamSet is used in Bevy and Wasvy, then modify QueryResolver to hold and manage the mutable reference to the queries, ensuring all access goes through its interface.
Tech stack
rust
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustBevy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50