Possible split of this tool for other uses #30
Description
Right now there seems to be a bit of a discrepancy of data being generated due to the source of data and what this tool actually targets. For example, the data contracts from the server who owns the thrift contract and the browser itself looks something like this thrift -> tchannel -> thriftrw -> browser where at any arrow the data contract can (and does) change.
Right now thrift2flow really focuses on that last arrow thriftrw -> browser. But it bases it's information from the thrift file directly which it gets from the server. In reality, it should base it's information off the tchannel translation of this thrift file definition.
Based on this there needs to be a few tools written
- Flow generator based on the thrift file itself (possible integration with the thrift product similar to how they did typescript)
- thriftflow2tchannel converter
- tchannel2thriftrw converter
This would then allow for the most accurate portral of the conversions going on along with if a layer was removed in the middle somewhere, most accurate maintenance of final generation.