-
Notifications
You must be signed in to change notification settings - Fork 2
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
Plan Management #199
Comments
Under the plan entity, can we create another entity called features which will have a relationship with the entity? |
For the features, add features field which is a list of string and annotate with @ElementCollection |
Also add plan type field which is an enum of Monthly and Yearly |
Noted, for the api, what fields was I to request from the user? |
plan name, plan price, plan type, and features, features should accept array of string |
and for the syb-domain is it still underthat ama? |
The sub domain bit will come when a client is doing subcription, when a client will be subscribing to a plan, that's when he/she will set a preffered sub domain. |
Added end point to manage subsciption plans
Add plan entity will have a name, price, updatedAt, and createdAt , createdBy fields
The text was updated successfully, but these errors were encountered: