Add metadata to plans. about cashier-mollie

[sandervanhooft]

Hi @MSnoeren,

We're essentially discussing two features here:

• metadata: I like the idea of having metadata, because it can also be accessed by the preprocessors.

• features: would be essentially another feature, and very application specific. I don't think this should be a first class citizen as of yet. But if we go with the metadata, you could nest the features there. (metadata => features => ...)

[sandervanhooft]

@pascallieverse Can you open a separate issue for this?

[sandervanhooft]

@MSnoeren what do you think?

[MSnoeren]

Looks fine to me. That way features can be added as well, but simply by adding them to the metadata.

[sandervanhooft]

FYI: Not sure yet I'll be including this in the v1 release. Not a must-have at this point.

[Jimmylet]

Hi @sandervanhooft, big thanks for this package! When do you think the V1 will be available?

I can't wait to use this package in production.

[sandervanhooft]

@Jimmylet Please stay on topic; the answer you're looking for is here: #32.

[pascallieverse]

It would also be nice to have metadata for each subscription and not connected to a predefined plan.
So you could save a variable as "domainname" for example. Currently I am using the name of the subscription as foreign key to add more information to a subscription.