[w3c/webpayments-payment-apps-api] Renaming PaymentApp* classes (#109)

Now that we've renamed to our specification to Payment Handler API, I think it would make sense to not name our classes starting with PaymentApp. I don't think it's super elegant to just rename everything to PaymentHandler*, so I'm looking at alternatives. The first classes I wanted to consider was the following:

```
5.2 PaymentAppManager interface
5.3 PaymentAppOptions interface
5.4 PaymentAppOption dictionary
5.5 PaymentWallets interface
5.6 WalletDetails interface
```

I think `PaymentAppManager` can just become `PaymentManager`, but `PaymentAppOptions` can not be renamed to `PaymentOptions`, as that would cause a name conflict with a class in the Payment Request API specification.

When talking about digital payments, one often talk about a digital wallet containing a set of digital payment instruments. So, how about `PaymentInstrument`? I realize it's a term with very specific meaning, but I think that it actually fits quite well here.

I would also suggest renaming `WalletDetails` to be consistent with the other names, so that we would end up with the following set of classes:

```
5.2 PaymentManager interface
5.3 PaymentInstruments interface
5.4 PaymentInstrument dictionary
5.5 PaymentWallets interface
5.6 PaymentWallet interface
```

WDYT?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments-payment-apps-api/issues/109