Write a currency pair and its convention together, and check the pair code
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
A pair and its convention are written by two operations; if the second fails the pair exists without the convention it must have one of. The pair insert validates the legs and the classification but not that the pair code is BASE/QUOTE, that the legs differ, or that they are in base-precedence order. The pair list filter takes pair codes only. The convention model's note names a trading table for business_day_convention, while the insert validates against the refdata list. Add one operation that writes both, derive or check the pair code on the server, add currency and classification filters, and correct the model note.
2. Why
Found while writing the currency pair journey; each item is a gap the screen has to work around.
3. References
- Journey: Set up a currency pair, gaps 1 to 4
projects/ores.refdata/modeling/ores.refdata.currency_pair_convention.org