Add support for processing multiple input lines

[uggyuggy]

Hi,

Thank's for sharing this tool.

Adding below few ideas/feature requests. As they are quite "close" and/or linked to each other (I think), I list those in a single "issue".

It would be nice to have an option for "direct" results without extra informations lines and/or that even could be the default ouput and the current output with some kind of -interactive

$ usl 'https://emea01.safelinks.protection.outlook.com/?url=http%xxxxxxxxx'
example.net

Current output could also be

$ usl -interactive

Enter URL: https://emea01.safelinks.protection.outlook.com/?url=http%xxxxx
Original URL: http://example.net

It would be nice to be able to be able to bulk process multiple links at once in parallel

• From piped data

$ cat file.with.links | usl
http://example.com
http://example.net

• From input file

$ usl -inputfile file.with.links
http://example.com
http://example.net

[atc0005]

@uggyuggy Thanks for filing this.

Will give this some thought and will ping you when there is something to test.

No estimates on timeline (other items have current focus).

[atc0005]

Overall I like the ideas, but I'd like to keep the current behavior of prompting the user if no input is provided. When I had others test the tool this behavior seemed intuitive to them and did not require further explanation.

Based on that, I think this would be the result:

• retain interactive prompt if no input given
• emit results without leading explanation text (i.e., drop Original URL: text and following newline)
• if input given, process and emit results without decoration until no further input provided (e.g., via pipe)
• if input file given, process the same way as stdin

As I mentioned I have other items ahead of this, so would probably work on this in pieces.

[uggyuggy]

Hi @atc0005

Thank's for sharing design plans.

I'd like to keep the current behavior of prompting the user if no input is provided.
...
retain interactive prompt if no input given

I fully understand you, you are right, that's probably better that way.

drop Original URL: text and following newline)

Yes, sending directly the result would be good, and should still makes perfect sense to any user.

if input given, process and emit results without decoration until no further input provided (e.g., via pipe)

Sounds good to me too.

if input file given, process the same way as stdin

Sounds good to me too.

As I mentioned I have other items ahead of this, so would probably work on this in pieces.

Thank's, feel free to ping me here so I could "help" testing further when you will work on this 👍

[atc0005]

@uggyuggy Dev build available here:

• https://github.com/atc0005/safelinks/releases/tag/v0.3.0-alpha.1

No doc updates yet, but hopefully the help text covers new behavior well enough.

[atc0005]

@uggyuggy Dev build available here:

• https://github.com/atc0005/safelinks/releases/tag/v0.3.0-alpha.1

No doc updates yet, but hopefully the help text covers new behavior well enough.

Later dev build:

• https://github.com/atc0005/safelinks/releases/tag/v0.3.0-alpha.2
  • linting fixes, otherwise should be equivalent to first build

[atc0005]

No doc updates yet, but hopefully the help text covers new behavior well enough.

Updated README coverage:

• https://github.com/atc0005/safelinks/blob/v0.3.0-alpha.3/README.md

[atc0005]

Changes included in v0.3.0 release:

• https://github.com/atc0005/safelinks/releases/tag/v0.3.0

[uggyuggy]

Hi @atc0005

Tested it, looks great.
Thank's 👍