Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Resolve system order ambiguities #542

Open
rj00a opened this issue Oct 4, 2023 · 0 comments · May be fixed by #599
Open

Resolve system order ambiguities #542

rj00a opened this issue Oct 4, 2023 · 0 comments · May be fixed by #599
Labels
enhancement New feature or request

Comments

@rj00a
Copy link
Member

rj00a commented Oct 4, 2023

Describe the problem related to your feature request.

Valence has a large number of internal system order ambiguities, making ambiguity detection unusable for end users.

What solution would you like?

Now that bevyengine/bevy#9895 is merged, we can mark Client as an ambiguous component and hopefully resolve the rest manually.

What alternative(s) have you considered?

Additional context

see bevyengine/bevy#9884
@rj00a rj00a added the enhancement New feature or request label Oct 4, 2023
@rj00a rj00a mentioned this issue Jan 29, 2024
Open
@rj00a rj00a linked a pull request Feb 11, 2024 that will close this issue
Rewrite Project #599
Draft
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rewrite Project valence-rs/valence
1 participant
@rj00a