Split CLI off into its own project?

Question

Split CLI off into its own project?

realityking opened this issue 7 years ago · 3 comments

I noticed that the parser itself is actually completely free of dependencies, they're only used in the CLI. What do you think of splitting the CLI into its own repository (maybe curl-trace-parser-cli)? It would reduce the update churn due to the new fixed versioning.

Answer 1 · 2018-04-24T14:03:27.000Z

@michalholasek What do you think of this one?

Answer 2 · 2018-04-24T15:14:37.000Z

I was wondering if it makes sense that curl-trace-parser was to become an adapter for Fury. Then you can use it in conjunction with other fury adapters such as API Blueprint serialiser (and possibly other serialisers). The tool at fury-cli would be able to replace the CLI part for free.

It would be an adapter that emits API Element's (minim objects) which other Fury adapters and tooling can consume.

Not sure what your use case is @realityking, would my proposal align with your uses?

Answer 3 · 2018-05-02T13:51:54.000Z

I'd like to talk this through with @netmilk.