no_symcache_no_problem: be more tolerant of not-yet-implemented provider backends #39

Merged

goodboy merged 5 commits from no_symcache_no_problem into main

2026-01-05 16:29:00 +00:00

Author	SHA1	Message	Date
Tyler Goodlet	07fbe859c3	Finally drop `Symbol` It was replaced by `MktPair` long ago in, https://github.com/pikers/piker/pull/489 with follow up for final removal in, https://github.com/pikers/piker/issues/517 Resolves #517	2026-01-02 16:49:16 -05:00
Tyler Goodlet	db0872e350	`.accounting._ledger`: typing anda more multiline styling	2026-01-02 16:49:16 -05:00
Tyler Goodlet	878002aee0	Drop some bps and style logic to multiline	2026-01-02 16:49:16 -05:00
Tyler Goodlet	c9e6510535	Invert `getattr()` check for `get_mkt_pairs()` ep Such that we `return` early when not defined by the provider backend to reduce an indent level in `SymbologyCache.load()`.	2026-01-02 16:49:16 -05:00
Tyler Goodlet	4cae3778c1	Allow ledger passes to ignore (symcache) unknown fqmes For example in the paper-eng, if you have a backend that doesn't fully support a symcache (yet) it's handy to be able to ignore processing other paper-eng txns when all you care about at the moment is the simulated symbol. NOTE, that currently this will still result in a key-error when you load more then one mkt with the paper engine (for which the backend does not have the symcache implemented) since no fqme ad-hoc query was made for the 2nd symbol (and i'm not sure we should support that kinda hackery over just encouraging the sym-cache being added?). Def needs a little more thought depending on how many backends are never going to be able to (easily) support caching..	2026-01-02 16:49:16 -05:00