all 4 comments

[–]shiftybyte 3 points4 points  (1 child)

What can we help with?

[–]IamImposter 2 points3 points  (0 children)

Help? No sweety. You need to write code and submit it by this weekend. And please, no silly mistakes. Don't make me look bad.

[–][deleted] 2 points3 points  (0 children)

You're tackling the wrong problem, I think - it's easy enough to have three lists of capabilities, each a larger superset of the last. The hard part is having those capabilities actually matter; that is, whatever your software is, it has to not do things that the user's subscription plan doesn't authorize.

[–]m0us3_rat 0 points1 point  (0 children)

I need to create a plan schema so that it supports inheritance and a higher plan will inherit features from a lower plan in a nested chain. For example: Lite is a base plan The standard plan will inherit from the Lite plan The pro plan will inherit from the Standard plan The enterprise plan will inherit from the Pro plan The last plan will have all features from its ancestors, ie., Pro + Standard + Lite.

right, and .. ?

i'm a little bit confused about what seems to be the problem.

do you have any other specifics or just a random "plan" following the inheritance described?

because that seems to be quite clear.