Justin Shreve fb124232cf Update Payment Tokens to follow the same pattern for custom data as other object types. ... Payment tokens was introduced in 2.6 and was updated to use the new CRUD code while some of the CRUD system was still in flux. While most things were correct, the prop handling for custom fields (like a card's last 4 digits) were directly calling meta functions, instead of delegating to the data store/parent. This PR moves these props to `extra_data` and follows the same pattern as product types or order items. It also updates some version tags to 3.0.0. Finally, it adds an additional test for saving meta after a create which looks like it was lacking. To Test: * Run `phpunit`. * Go to the "My Account" tab and add a new payment method. You need a payment gateway that supports this, like Simplify. * Test the add a payment method flow. * Make a test purchase using the saved payment method.		2017-03-14 12:33:35 -07:00
..
abstract-wc-legacy-order.php	has_meta -> meta_exists	2017-03-14 16:49:13 +00:00
abstract-wc-legacy-payment-token.php	Update Payment Tokens to follow the same pattern for custom data as other object types.	2017-03-14 12:33:35 -07:00
abstract-wc-legacy-product.php	Legacy variation meta handling	2017-02-28 10:29:08 +00:00
class-wc-legacy-coupon.php	Fix direct property access for coupon amount.	2017-03-09 10:34:45 -08:00
class-wc-legacy-customer.php	Wrap all deprecation calls.	2016-11-23 16:15:00 +00:00
class-wc-legacy-shipping-zone.php	Fix wording on deprecation messages	2017-01-30 23:40:21 -06:00