229 make all analyses available for reports

[m-milek]

This pull request includes significant changes to the backend and nlp modules to improve the NLP analysis capabilities and refactor the code for better maintainability. The main changes involve updating the NlpClient to support parallel analysis requests and refactoring the input processing functions in the nlp module.

Backend Module Changes:

• backend/src/api/report/generate.rs: Updated the nlp_analysis function to accept multiple analysis kinds and perform parallel analysis using the new analyze_parallel method. [1] [2] [3]
• backend/src/nlp/nlp_client.rs: Added an api_key field to NlpClient and updated the analyze method to use this key. Introduced a new analyze_parallel method to handle parallel analysis requests. [1] [2] [3] [4]

NLP Module Changes:

• nlp/src/main.py: Refactored multiple analysis functions (get_sentiment, get_language, get_sarcasm, get_keywords, get_spam, get_politics, get_hate_speech, and get_clickbait) to use a new process_inputs helper function for better code reuse and maintainability. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]

[deepsource-io]

Here's the code health analysis summary for commits 53101a1..601f2dd. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Secrets	✅ Success		View Check ↗
Docker	✅ Success		View Check ↗
Rust	✅ Success	❗ 4 occurences introduced 🎯 3 occurences resolved	View Check ↗
JavaScript	✅ Success		View Check ↗
Python	✅ Success	❗ 60 occurences introduced 🎯 12 occurences resolved	View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[Smixie]

For me everything looks fine. The one thing I can think of is change generated_in to camel case. I remember it is a format required for frontend.

[m-milek]

For me everything looks fine. The one thing I can think of is change generated_in to camel case. I remember it is a format required for frontend.

It's better if it stays in snake case. Before reaching the frontend, it gets parsed to a backend struct and saved to our database. I'll handle the conversion on my side