-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Split CLI off into its own project? #16
Comments
@michalholasek What do you think of this one? |
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? |
I'd like to talk this through with @netmilk. |
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.The text was updated successfully, but these errors were encountered: