[Feature request]: Enable using .spawn_continuous_service via mut Command via proxy systems
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No project files or tests are named. Start by reading the current spawn_continuous_service API and the linked bevy_proxy_system example, then trace how App schedules and SystemIds are handled. Done should support the requested per-need service initialization through a bevy_impulse proxy without requiring access through &mut App.
Written by the indexing model from the issue text.
Description
Before proceeding, is there an existing issue or discussion for this?
- I have done a search for similar issues and discussions.
Description
Curently, .spawn_continuous_service can only be used through &mut App which is problematic for enabling services on a "per-need basis". E.G:
if you had a Service that dependent on a picking service:
pub struct PickingService(Service<(), ()>);
... inside a plugin init
let picking_service = self.spawn_continuous_service(
Update,
picking_service::<F>.configure(|config: ScheduleConfigs<ScheduleSystem>| {
config.in_set(SelectionServiceStages::Pick)
}),
);
You would either need a singleton plugin for this service ,or make a create a large resource that contains this service + a lot of other unrelated services.
to reduce .add_plugin spam and to allow initializing services via cascading FromWorlds, systems could be run within bevy_impulse via a proxy system that iterates over registered app schedules(similar to type registry) and runs systems via SystemIds.
E.G: Something along the lines of this example:
https://github.com/rydb/bevy_proxy_system/blob/main/src/main.rs
Implementation Considerations
No response
Alternatives
No response
Additional information
No response
- Dominant language
- Rust
- Stars
- 75
- Forks
- 18
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from open-rmf/crossflow
-
Diagram editor fails to build on Windows: build.rs can't find pnpm (pnpm.cmd)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
All issues in open-rmf/crossflow
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
storytold/photocraft#14822 ·
Maintainers usually reply within 1 day
-
bug css
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
dginev/latexml-oxide#853 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 2 days
-
[Bug] export_build_environment admits its output directory only after the export ran in the build computerPossibly taken @viniciusdsandrade claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day