-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
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
Update tax rates documentation for fix 29472 #199
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes looks good, there's only one issue with the type of the field, it's an array of strings now, so I'm suggesting to change to string[]
to indicate it.
Also I'm suggesting to indicate what version we deprecated or included parameters in REST API to avoid confusing in our REST API consumers.
In the REST API entry point to update tax rates. Co-authored-by: Claudio Sanches <[email protected]>
In the REST API entry point to update tax rates.
Hi @claudiosanches, I've committed your suggestions and added the introduction+deprecation notices. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great now, but I'll hold a little to merge it since we'll only implement this feature in 5.3.
woocommerce/woocommerce#27751 and woocommerce/woocommerce#29495 introduce two new fields for the tax rates:
postcodes
andcities
. This pull request adds them to the documentation and also changes it so that:city
andpostcode
are deprecated.orderby
andclass
for the taxes retrieval endpoint.priority
to the list of possibleorderby
values for the taxes retrieval endpoint (this value was introduced in Add "postcodes" and "cities" support for the REST API tax rate creation/update endpoint woocommerce#29495).