Skip to content
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

Finish inline property docs #321

Merged
merged 1 commit into from
Jul 18, 2017
Merged

Finish inline property docs #321

merged 1 commit into from
Jul 18, 2017

Conversation

bhelx
Copy link
Contributor

@bhelx bhelx commented Jul 12, 2017

Continuing on the work of @phpdave to document the resource properties in #279.

@bhelx bhelx requested a review from drewish July 12, 2017 17:40
@@ -1,5 +1,11 @@
<?php

/**
* Class Recurly_AccountBalance
* @property Recurly_Stub $account The associated Recurly_Account for this acquisition object.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"for this account balance."

@@ -1,5 +1,16 @@
<?php

/**
* Class Recurly_AccountAcquisition
* @property Recurly_Stub $account The associated Recurly_Account for this acquisition object.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We refer to this object as "acquisition object", "account acquisition", "account acquisition info" can we just pick one and use it consistently?

* @property string $name The add-on name. Max of 255 characters.
* @property int $default_quantity Default quantity for the hosted pages, defaults to 1.
* @property int $default_quantity_on_hosted_page If true, displays a quantity field on the hosted pages for the add-on.
* @property string $tax_code Optional field for EU VAT merchants and Avalara AvaTax Pro merchants. If you are using Recurly's EU VAT feature, you can use values of 'unknown', 'physical', or 'digital'. If you have your own AvaTax account configured, you can use Avalara's tax codes to assign custom tax rules.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've got a few styles of listing to valid enum values:

  • Allowed values: [referral,...
  • values of 'unknown', 'physical',...
  • is Fixed-Price (fixed), or Usage-Based (usage)

It would be nice to standardize it a bit. Are we going to quote the values? etc

* @property float $usage_percentage If add_on_type = usage, you will see usage_percentage, which can have a value if usage_type = percentage. Must be between 0.0000 and 100.0000.
* @property string $revenue_schedule_type Optional field for setting a revenue schedule type. This will determine how revenue for the associated Plan should be recognized. When creating a Plan, if you supply an end_date and end_date available schedule types are never, evenly, at_range_start, or at_range_end.
* @property DateTime $created_at The date and time the addon was created.
* @property DateTime $updated_at The date and time the addon or its billing info was last updated.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

its billing info seems like copy pasta.

* @property string $usage_type string If add_on_type = usage, you will see usage_type, which can be price or percentage. If price, the price is defined in unit_amount_in_cents. If percentage, the percentage is defined in usage_percentage.
* @property float $usage_percentage If add_on_type = usage, you will see usage_percentage, which can have a value if usage_type = percentage. Must be between 0.0000 and 100.0000.
* @property string $revenue_schedule_type Optional field for setting a revenue schedule type. This will determine how revenue for the associated Plan should be recognized. When creating a Plan, if you supply an end_date and end_date available schedule types are never, evenly, at_range_start, or at_range_end.
* @property DateTime $created_at The date and time the addon was created.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typically we use the hyphen in "add-on".

* @property Recurly_Stub $account The URL of account belonging to this redemption.
* @property Recurly_Stub $subscription The URL of subscription belonging to this redemption.
* @property string $uuid The unique UUID referencing this redemption.
* @property boolean $single_use True if this is a single_use coupon.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make this "a single use coupon."

* @property Recurly_Stub $subscription The URL of subscription belonging to this redemption.
* @property string $uuid The unique UUID referencing this redemption.
* @property boolean $single_use True if this is a single_use coupon.
* @property integer $total_discounted_in_cents Total in cents for the discount issued with this redemption
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit but all the other properties end with a period

@@ -1,5 +1,14 @@
<?php

/**
* Class Recurly_SubscriptionAddOn
* @property Recurly_Stub $gift_card The gift card object is required in order to redeem a redemption code.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this really on the subscription add-on?

* Class Recurly_SubscriptionAddOn
* @property Recurly_Stub $gift_card The gift card object is required in order to redeem a redemption code.
* @property string $add_on_code The code for the Add-On.
* @property int $unit_amount_in_cents Amount of the transaction in cents. Max 10000000.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure transaction is the right word here

@@ -1,5 +1,19 @@
<?php

/**
* Class Recurly_Usage
* @property Recurly_Stub $measured_unit The url to the Recurly_MeasuredUnit associated with this usage.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You capitalized all the other URLs so lets have this one match

Finishing on the work of @phpdave to document the resource properties in #279.
Copy link

@drewish drewish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@drewish drewish merged commit 77cae0c into master Jul 18, 2017
@drewish drewish deleted the finish_property_docs branch July 18, 2017 16:21
@bhelx bhelx added the V2 V2 Client label Mar 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
V2 V2 Client
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants