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

Add a trait for input mocking #536

Closed
alice-i-cecile opened this issue Jun 10, 2024 · 1 comment · Fixed by #570
Closed

Add a trait for input mocking #536

alice-i-cecile opened this issue Jun 10, 2024 · 1 comment · Fixed by #570
Labels
code-quality Make the code faster or prettier controversial Requires a heightened standard of review usability Reduce user friction
Milestone
0.15

Comments

@alice-i-cecile
Copy link
Contributor 

          It should be able to replace with a new trait for implementing input mocking

Originally posted by @Shute052 in #490 (comment)
@alice-i-cecile alice-i-cecile added code-quality Make the code faster or prettier usability Reduce user friction controversial Requires a heightened standard of review labels Jun 10, 2024
@alice-i-cecile alice-i-cecile added this to the Trait-driven design milestone Jun 10, 2024
@alice-i-cecile
Copy link
Contributor Author

Unsurprisingly, input mocking should also be traitified. Once #535 is done the design should be much clearer.

@alice-i-cecile alice-i-cecile moved this to Active: LWIM upstreaming in Alice's Work Planning Jul 8, 2024
This was referenced Jul 24, 2024
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
code-quality Make the code faster or prettier controversial Requires a heightened standard of review usability Reduce user friction
Projects
None yet
Milestone
0.15
Development

Successfully merging a pull request may close this issue.

Move input mocking to new traits Leafwing-Studios/leafwing-input-manager
1 participant
@alice-i-cecile