fix: This PR fixes linting errors

[KrishnaShuk]

Summary

This PR simply fixes linting errors.

AI Disclosure

• No AI used
• AI/IDE/Agents used (please describe below)

Checklist

• PR title follows format: type(scope): description or [scope] description
• Tests pass (pytest tests/)
• MVP label added if closing MVP issue
• Update "Cortex -h" (if needed)

[coderabbitai]

Caution

Review failed

The head commit changed during the review from 55137ae to d8d32bd.

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @KrishnaShuk, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing code readability and maintaining a consistent coding style by fixing various linting errors. The primary change involves reformatting multi-line string literals, particularly SQL queries and print statements, to adhere to a standardized style. This effort ensures a cleaner codebase without introducing any functional modifications.

Highlights

• Code Formatting Consistency: Applied consistent formatting to multi-line string literals across numerous Python files, primarily affecting SQL queries and print statements.
• Linting Error Resolution: Directly addresses and resolves existing linting errors, enhancing the overall code quality and adherence to style guidelines.
• No Functional Changes: The modifications are purely cosmetic and do not alter the behavior, logic, or functionality of the application.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Code Review

This pull request applies linting fixes across multiple files, primarily addressing line length and formatting for multiline strings and function calls. The changes are consistent with standard Python formatters like black and improve code style without altering functionality. The changes look good and correctly address the linting issues.

[Anshgrover23]

@KrishnaShuk Already fixed.