Skip to content
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

feat: pipe input and output with cmd rimo analyse #10

Open
youen opened this issue Aug 23, 2023 · 1 comment
Open

feat: pipe input and output with cmd rimo analyse #10

youen opened this issue Aug 23, 2023 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@youen
Copy link
Collaborator

youen commented Aug 23, 2023

Issue Description:
Currently, the Rimo tool provides a convenient way to create statistics. However, there seems to be a missing feature that could enhance the tool's usability further. It would be great if Rimo could support reading input data from the standard input using a special file name, such as -, which is a common convention in many command-line tools.

Feature Request:
I would like to request the addition of support for using the special file name - to read input data from the standard input for the rimo analyse command. This would allow users to provide input data directly through standard input, without the need to specify an input directory and input file names explicitly.

Proposed Behavior:
When the special file name - is used as the input argument for the rimo analyse command, Rimo should read input data from the standard input stream. This would enable users to pipe or redirect data directly into the tool, making it more versatile and in line with common command-line practices.

Example:

rimo analyse - output_directory

Benefits:

  • Improved usability: Users can input data without the need to create intermediary files.
  • Consistency: The use of - as a special file name is widely recognized in command-line tools.
  • Streamlined workflows: Users can easily integrate Rimo into their pipelines and scripts.

Implementation Considerations:

  • The tool should detect the use of - as a file name specifically for the input argument of the rimo analyse command.
  • When - is used as the input argument, Rimo should read data from the standard input stream.
  • Care should be taken to handle potential conflicts with existing functionality or argument parsing.

Additional Context:
This enhancement would align Rimo with best practices for command-line tools and provide users with a more seamless experience when working with input data. It would particularly benefit users who prefer to work with pipelines and automate their workflows.

Thank you for considering this feature request. Please let me know if any further information is required or if there are any suggestions regarding the proposed functionality.

Environment Information:

  • Rimo version: 0.1.0
  • Operating System: linux

Labels:

  • feature request
  • command-line tool
  • usability
@mathisdrn mathisdrn self-assigned this Aug 23, 2023
This was referenced Aug 24, 2023
@mathisdrn mathisdrn added documentation Improvements or additions to documentation enhancement New feature or request labels Aug 25, 2023
@mathisdrn mathisdrn changed the title Request to Support Special File Name '-' for Standard Input Reading cmd rimo analyse : input and output pipe support Aug 25, 2023
@mathisdrn
Copy link
Contributor

Révision/Question sur l'issue :

Je veux pouvoir piper l'input et/ou l'output de la commande rimo analyse :

  • input pipe : `xxx > rimo analyse - outputDir
  • output pipe rimo analyse inputDir - > xxx
  • input and output pipe : xxx > rimo analyse - - > xxx

Question : le nom de la base et table sont extrait du nom du fichier (ie. basename_tablename.jsonl). Comment procéder au pipe de l'input sans ces informations ?

@mathisdrn mathisdrn changed the title cmd rimo analyse : input and output pipe support feat: pipe input and output with cmd rimo analyse Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants