Support FIX50 - Githubissues

drewnoakes / fix-decoder

Unravels FIX messages into human readable tables

80 stars 34 forks source link

Support FIX50 #27

Open drekbour opened 4 years ago

drekbour commented 4 years ago

Seeing general conversation on "doesn't support field NNN" always returns to this, fix-decoder should support the current standard.

[ ] Dump FIX 5 fields onto the end of data.js as a fig-leaf
[ ] Add capability for multiple (vanilla) dictionaries with version-detection

drekbour commented 4 years ago

Q: Both of these really need to involve generating the data.js content from XML dictionaries (e.g. https://github.com/quickfix/quickfix/tree/master/spec). @drewnoakes How did you seed the very first data.js ?

drewnoakes commented 4 years ago

How did you seed the very first data.js ?

I don't remember unfortunately. Most likely I cobbled something crude together to convert XML to JSON.

Having a file-per-version makes sense. Perhaps we have a build step to do this conversion in a repeatable fashion.

drekbour commented 4 years ago

OK. The linked quickfix repo already contains XSL for converting the dictionaries into bindings in multiple languages so there's a quickstart right there. Actually... we could use git submodules to pull in their spec directory (or some more canonical version) instead of yet another copy of the files. I've made decent progress on this (and a host of tidying) already but it will be many months before I can externalise this from my employer.

drewnoakes commented 4 years ago

The submodule idea is a good one.

I've made decent progress on this (and a host of tidying) already but it will be many months before I can externalise this from my employer.

Whatever you're able to share will certainly be appreciated by the wider FIX development community.