Repository navigation
Tokei output compatibility #104
Description
Activity
The tabular output would be difficult to read because
rust-code-analysishas lots of metrics compared toTokei. Thejsonoutput is already implemented.Having a table per-metric should solve the problem of having way too many columns I guess.
I do not have strong opinions in this regard, but would be nice to have a way to see the data from the cli w/out piping the json to something that formats it though.
I do not have strong opinions in this regard, but would be nice to have a way to see the data from the cli w/out piping the json to something that formats it though.
Right, but for now the tabular option has low-priority compared to your third item :)
The tabular format presents a series of problems.
Let
mbe the number of files in a directory,nthe number of function spaces andkthe number of tables. Let also suppose that each struct is represented by a table.The final number of tables is then equal to:
m * n * k
if the values of the three variables are pretty large, we would get an enormous output, difficult to analyze.Possible approaches could be the following ones:
- Print only global metrics for each file
- Print only determined metrics for each file and function space
- Do not implement the tabular approach for
rust-code-analysis
See tokei