mkadirtan / feed-toolbelt Goto Github PK

          Currently, either TargetURL or TargetHTML needs to be defined. But it causes confusion in implementation and usage. A better solution could be:

• Require TargetURL no matter what
• Make it optional to pipe in the request body, such as

curl https://nooptoday.com | feed-toolbelt find --piped https://nooptoday.com

When --piped option is used, TargetURL becomes optional. Otherwise, piped input is recognized as the targetURL, such as:

echo https://nooptoday.com | feed-toolbelt find

Which could turn out to be a common scenario, where reading links from a text file and piping them line by line into feed-toolbelt for example.

Originally posted by @mkadirtan in #4 (review)

Add github action for continuous integration. Check for:

• Run formatter
• Run tests
• Scan vulnerabilities

You can use existing actions or write a new action.

It is getting harder and harder to keep track of flags and usage messages, using a library can benefit at this stage.