Skip to content

Conversation

@boomermath
Copy link
Contributor

To prevent the use of one component of the shooter from stopping the use of the other

@boomermath boomermath requested a review from a team as a code owner September 23, 2024 00:43
@boomermath boomermath requested a review from a team September 23, 2024 00:43
}


private static class FeederSubsystem extends SubsystemBase {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we break this out into its own file?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really think of the two subsystems as the same thing. It's always been a bit confusing to me why we didn't split it off initially. I think having separate files would help with findability as well as general organization.

Comment on lines 95 to 97
protected Command spinFeederAndStop(double speed) {
return startEnd(() -> feederMotor.set(speed), feederMotor::stopMotor);
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can be more specific with the command(s) we define here. We're pretty much only ever going to have one intake and one eject. I'd handle the beam break logic within here. We can still publish this if we need it, but I'd rather have a more explicit interface here.

@qwertycloudhub qwertycloudhub linked an issue Sep 24, 2024 that may be closed by this pull request
@boomermath boomermath self-assigned this Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feeder subsystem

3 participants