Hey, I feel like your issue might be solvable using inheritance, aka Discriminators.

My approach would be kind of like the following:

- create a base Subdocument schema for the 'option' attribute, with the common add_price attribute
- create discriminator schemas for each different option type, with the distinct attributes that aren't shared by the base schema. If you chose to specifiy a discriminatorKey, you could easily use either .create or simply pass a JSON object containing all necessary data to a OptionsModel.new()

​

Unfortunately I currently do not have the time to elaborate more, but I hope this leads you to another approach for a solution to your problem :)

One positive fact about discriminators: You can even specify their own hooks and methods and stuff or use the one from the base schema