User Story: Specify want with regexp pattern, including string prefix

[rowgraus]

Story

As a user, I want to be able to buy something described using the MathKind.STRING_SET with offer safety, even though I only care about and only specify a prefix of the strings. (In standard financial markets financial derivative characteristics (e.g., expiration date, strike price, ...) may be specified as part of the security name.)

Status

This is not something we currently support.

Next Steps

This may be an anti-pattern, as MathKind.SET with separate properties for each part of the description is probably preferable. For that reason and because we do not have a good example of DENOMs to work from, this is not an official user story in #2230, but will fall out of it anyways.

[erights]

This would be a natural extension of the pattern notion explored in the #1905 spike, if that works out.

[katelynsills]

@katelynsills does this accurately describe this work item? How much do we need to know about the specifics of how things may be specified before we can do this?

That's a good question. If we have more general flexibility with the MathHelper.SET version that Mark is working on (where every separate piece of data has its own record property that can include non-strings as values, such as identifying a particular timer or priceOracle), perhaps we don't want this version, since the MathHelper.SET version is more flexible. We might want to implement this only for making people feel comfortable, and convince them to move the MathHelper.SET version as soon as possible. This might be an anti-pattern if we have the better implementation.