The generated shell lost the one-line bulk input for basket constituents and option underlyings
Table of Contents
This page is a capture in the inbox bucket of the product backlog — a pre-sprint idea, not yet pulled into a sprint as a story.
1. What
Two hand-written shell units took a list of child rows in one positional
argument. commodity_instrument add took CODE:weight,CODE:weight and
wrote the commodity_basket_constituent rows. The
equity_position_option_underlying unit took parse_entries rows. The
generated units replaced both. Each child entity now has its own generated
menu with per-row add and set, so all rows can be written, but each row
needs one command. To restore the one-line form, model the child list as a
command argument of the parent. That is a design change to the shell
command generation, not a repair.
2. Why
The review of PR #2496 found that the basket editor was lost when the hand-written unit was deleted. The fix enabled the shell facet on the constituent, which restores the capability but not the convenience. A user who books a basket with many constituents now types one command per constituent.
3. References
ores.trading.commodity_basket_constituent.org,ores.trading.equity_position_option_underlying.org.- Commit
8727749250, which restored the per-row editor.