mkadirtan / feed-toolbelt

Powerful commands for working with various feed types such as RSS, Atom and JSON feeds

Hi, I'm Muhammed Kadir Tan 👋

• 💰 I'm currently building a wallet service to simplify in-app transactions for Getcontact at @Teknasyon
• 🖥 I'm a backend developer experienced in building low-latency applications
• 🦉 I'm learning Go ( for keeping sane ) and Python ( for playing with NLP )
• ✍🏻 I love reading great articles, you can read my articles at Noop Today
• 🛠 I would love any feedback on feed-toolbelt, a toolkit for working with RSS, Atom, and JSON feeds

feed-toolbelt's Issues

Continuous Integration

Add github action for continuous integration. Check for:

• Run formatter
• Run tests
• Scan vulnerabilities

You can use existing actions or write a new action.

Accept Piped Input with Option

          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)

Use a CLI arguments library

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