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

Purpose of the subscriptions name property #5

Closed
Konafets opened this issue Apr 18, 2017 · 2 comments
Closed

Purpose of the subscriptions name property #5

Konafets opened this issue Apr 18, 2017 · 2 comments
Labels

Comments

@Konafets
Copy link
Contributor

The doc says:

The first argument passed to newSubscription method should be the name of the subscription. If your application offer a single subscription, you might call this main or primary. The second argument is the plan instance your user is subscribing to.

In my scenario I have multiple plans where a user can subscribe to. He can only subscribe to one plan at a time, so he will never have more than one subscription. Does this means, the name of the subscription can be just primary?

@gerardojbaez
Copy link
Owner

Subscription name is a unique identifier for a particular section in your application. For example, if you offer mutiple services under the same application, (maybe with separate billing), you may use the subscription name to indentify each. When only one subscription is needed, you can name it primary or main. Just like you have mentioned.

@Konafets
Copy link
Contributor Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants