Add proper enumerations for trade key fields
Table of Contents
This page is a capture in the next bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
What
(One paragraph: the idea.)
Why
(Motivation, problem being solved, related context.)
References
See also
Trade forms currently use raw strings for fields that should come from tables, including:
- Product/instrument type (
FX Forward,Equity Option, etc.) - Call / put direction
- Position side (buy / sell)
Changes:
- Each field type gets a backing table and a corresponding domain type.
- Call/put specifically should be driven by a
ores_trading_call_put_types_tbl(or similar) seeded at database setup. - Qt forms use a combo box populated from a service query, not a hard-coded list.
- Conditional field display: option-specific fields only appear when an option type is selected.