Skip to content

style: format code with Autopep8, isort and Ruff Formatter#15

Open
deepsource-autofix[bot] wants to merge 1 commit into
mainfrom
deepsource-transform-df83c674
Open

style: format code with Autopep8, isort and Ruff Formatter#15
deepsource-autofix[bot] wants to merge 1 commit into
mainfrom
deepsource-transform-df83c674

Conversation

@deepsource-autofix

@deepsource-autofix deepsource-autofix Bot commented Dec 27, 2024

Copy link
Copy Markdown
Contributor

This commit fixes the style issues introduced in 376ba58 according to the output
from Autopep8, isort and Ruff Formatter.

Details: None

Summary by Sourcery

Chores:

  • Apply automatic formatting changes to the codebase.

This commit fixes the style issues introduced in 376ba58 according to the output
from Autopep8, isort and Ruff Formatter.

Details: None
@sourcery-ai

sourcery-ai Bot commented Dec 27, 2024

Copy link
Copy Markdown

Reviewer's Guide by Sourcery

This pull request fixes style issues in src/everyai/config/config.py using Autopep8, isort, and Ruff Formatter. The main change is formatting imports to align with PEP 8 standards.

Class diagram showing import organization in config module

classDiagram
    class config{
        +get_config(file_path: Path)
    }
    note for config "Imports reorganized for better readability:
    - BERT_TOPIC_CONFIG_PATH
    - DATA_LOAD_CONFIG_PATH
    - DATA_PATH
    - GENERATE_CONFIG_PATH
    - MONGO_CONFIG_PATH"

    config ..> Path : uses
    config ..> yaml : uses
    config ..> everyai_path : imports constants from
Loading

File-Level Changes

Change Details Files
Formatted imports to adhere to PEP 8 standards by wrapping long import statements.
  • Wrapped long import statements onto multiple lines with appropriate indentation.
  • Ensured consistent ordering and grouping of imports according to isort and PEP 8 guidelines.
src/everyai/config/config.py

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, deepsource-autofix[bot]!). We assume it knows what it's doing!

@deepsource-io

deepsource-io Bot commented Dec 27, 2024

Copy link
Copy Markdown
Contributor

Here's the code health analysis summary for commits 376ba58..a04a882. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource Python LogoPython✅ SuccessView Check ↗

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants