poor button 😿

srs bsns!

For now, I don't think we should warn about this.

I think it creates the implication that users should add a payment method without actually paying for anything, but there's currently no point to doing that, because we don't have a concept of payment methods that we'll automatically attempt to charge without further configuration.

Specifically, users may hit this:

See "no payment method" warning.
Add a payment method.
Warning vanishes.
Seems like they're all set.
At the end of the month, payment fails because the card isn't associated with the subscription.

This seems potentially more confusing than the current workflow.

There's also no obvious/direct way to actually add a payment method yet.

Instead, we could do one of these, which I think are better solutions:

• Warn "You have a subscription with no associated payment method."; or
• Add the idea of a "default" payment method, change subscriptions to have options "Never autopay; use default method; <use specific card>", warn "You have a subscription with no associated payment method, and have no default payment method."

I think adding "default payment method" is totally reasonable -- it didn't really make tons of sense before subscriptions, but now does.