Joseph Eng

Personally I'd like these to be `(and)Then...` followed by the named of the `Commands` factory (e.g., `thenWaitUntil(BooleanSupplier)` or `andThenWaitUntil(BooleanSupplier)`), since that should make it easier for people to remember.

The current wording is specific to parallel groups, so either we should change the wording so that it makes sense for any command (and isn't specific to checking requirements for...

Thanks for the detailed bug report! Triggers are only intended to be bound once at startup, so it's unlikely we'll want to fix this behavior. (Glad you found a workaround...

Ah, right, I forgot about the controller disconnected warnings. Since there's a workaround and this isn't a primary intended use of the API, I think this is fine? One of...

#7877 adds `GenericHID.warnWhenDisabled()` and `CommandGenericHID.warnWhenDisabled()` to let you indicate if a controller should emit a warning when disconnected. (This method is inherited by `XboxController`, `CommandXboxController`, and co.)

Someone more knowledgeable about the HAL than me would need to check if this would violate an assumption about the return value of `HAL_CreateSimDevice()`, but I think we could change...

Should this target the main branch or the 2027 branch?

2 things: 1) Do we want a warning version of `FRC_MakeError`? 2) Do we want `FRC_ReportWarning` to be defined in terms of `FRC_ReportError`? (See below) ```cpp #define FRC_ReportWarning(format, ...) \...

> Also, my browser gets sad trying to handle all 1226 files, so I'm just going to list all the spots here so the page doesn't crash. Yeah... I'm considering...

Something I'm just going to throw out here- Based on the https://github.com/orgs/wpilibsuite/projects/17/views/1 project board, this might be held off until fall anyways to reduce how much teams need to translate...