bevyengine / bevyengine/bevy

SystemId doesn't convey that it can be used as a oneshot system

Open
#18,599 0 comments 0 reactions 0 assignees View on GitHub
A-ECS C-Docs S-Ready-For-Implementation
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 22h
Merged PRs (30d)
161

Description

When having a conversation about Events. oneshot systems can come up.
If you were then to look for "oneshot" systems in the docs nothing comes up.

I propose that the word "oneshot" somehow gets incorporated within the SystemId context.
To make it both easier to talk about design. and being able to intuitively look up the information useful for it.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.