We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
With reference to the corresponding issue in the Browser spec, w3c/payment-request#33
How will versioning be done in the HTTP API? (The approach for browser is via JavaScript feature detection, but this does not apply to HTTP messages).
We could consider using a custom media type rather than "application/json", so for example "application/vnd.w3c.webpayments+json; version=1.0"
The text was updated successfully, but these errors were encountered:
No branches or pull requests
With reference to the corresponding issue in the Browser spec, w3c/payment-request#33
How will versioning be done in the HTTP API? (The approach for browser is via JavaScript feature detection, but this does not apply to HTTP messages).
We could consider using a custom media type rather than "application/json", so for example "application/vnd.w3c.webpayments+json; version=1.0"
The text was updated successfully, but these errors were encountered: