Fix Flask code-graph backend imports and Python 3.10 compatibility

[SarabdeepSBilkhu]

Closes #

📝 Description

Hi! I'm Sarabdeep Singh Bilkhu, a student contributor exploring Devr.AI.

While setting up the project locally, I found that the Flask-based code-graph backend could not start due to broken imports and Python 3.10 incompatibilities. This PR fixes those issues to unblock local development.

No functional behavior changes are intended.

Local Testing Setup

The following services were started to verify the fix:

Docker services

docker compose up -d

Main backend (FastAPI)

poetry run python main.py

Flask code-graph backend

FLASK_APP=app.database.falkor.code-graph-backend.api.index PYTHONPATH=. flask run --debug -p 5000

Frontend

npm install
npm run dev

The Flask code-graph backend starts successfully after these changes.

🔧 Changes Made

• Fixed broken absolute imports by converting them to correct relative imports
• Corrected incorrect import paths inside analyzers and entities
• Fixed Python 3.10 incompatibility by removing unsupported typing usage
• Verified that the Flask code-graph backend starts successfully

📷 Screenshots or Visual Changes (if applicable)

Not applicable (backend-only changes).

🤝 Collaboration

Collaborated with: (none)

✅ Checklist

• I have read the contributing guidelines.
• I have added tests that prove my fix is effective or that my feature works.
• I have added necessary documentation (if applicable).
• Any dependent changes have been merged and published in downstream modules.

Summary by CodeRabbit

• Refactor
  • Internal code improvements for enhanced maintainability with no impact to user-facing functionality.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR standardizes the codebase by converting absolute imports to relative imports across the code-graph-backend package (e.g., from api.entities.entity to from ..entities.entity). Additionally, the Self type annotation is relocated from typing to typing_extensions in the entity module. No functional logic changes.

Changes

Cohort / File(s)	Change Summary
Analyzer module imports backend/app/database/falkor/code-graph-backend/api/analyzers/analyzer.py, backend/app/database/falkor/code-graph-backend/api/analyzers/source_analyzer.py	Changed absolute imports to relative imports for entity and file modules (e.g., from api.entities.entity → from ..entities.entity)
Entity module imports backend/app/database/falkor/code-graph-backend/api/entities/entity.py, backend/app/database/falkor/code-graph-backend/api/entities/file.py	Relocated Self type import from typing to typing_extensions in entity.py; changed Entity import to relative in file.py (from api.entities.entity → from .entity)
Package index imports backend/app/database/falkor/code-graph-backend/api/index.py	Converted all absolute imports to relative imports for SourceAnalyzer, git_utils, GitGraph, Graph, get_repos, graph_exists, get_repo_info, ask, and Project modules
Test index imports backend/app/database/falkor/code-graph-backend/tests/index.py	Changed absolute imports to relative paths for Project and prefix_search modules

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Changes are homogeneous (consistent import refactoring pattern applied repeatedly)
• No logic, control flow, or error handling modifications
• Straightforward verification of import path correctness across files

Possibly related PRs

• [feat]: add codegraph support by FalkorDB for repo indexing #138: Updates import paths and typing imports in the same code-graph-backend modules (analyzer.py, source_analyzer.py, entity.py, file.py, index.py), making this a direct continuation or related refactoring effort.

Suggested reviewers

• chandansgowda

Poem

🐰 Whiskers twitching with delight,
Relative paths now shining bright!
From absolute imports we did flee,
To cleaner, local symmetry—
Self now typed, the code takes flight! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately summarizes the two main changes: fixing import issues (absolute to relative imports) and addressing Python 3.10 compatibility (typing_extensions for Self type).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

backend/app/database/falkor/code-graph-backend/tests/index.py (1)

2-2: Inconsistent import style: wildcard absolute import remains while relative imports were added.

Line 2 uses an absolute wildcard import (from api import *) while Lines 7-8 use relative imports from the same package (from ..api.project import Project and from ..api.auto_complete import prefix_search). This creates inconsistency within the file. Additionally, the codebase shows that absolute imports from api are the predominant pattern elsewhere in the tests directory, so the import strategy should be unified.

Consider either converting Line 2 to a relative import to match Lines 7-8, or converting Lines 7-8 to absolute imports to align with the broader codebase pattern. If migrating to explicit imports, list the specific symbols being used (Graph, graph_exists, get_repos, get_repo_info, SourceAnalyzer, ask) rather than using wildcards, which obscures symbol origins and risks namespace pollution.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8eeacad and 13e6859.

📒 Files selected for processing (6)

• backend/app/database/falkor/code-graph-backend/api/analyzers/analyzer.py (1 hunks)
• backend/app/database/falkor/code-graph-backend/api/analyzers/source_analyzer.py (1 hunks)
• backend/app/database/falkor/code-graph-backend/api/entities/entity.py (1 hunks)
• backend/app/database/falkor/code-graph-backend/api/entities/file.py (1 hunks)
• backend/app/database/falkor/code-graph-backend/api/index.py (1 hunks)
• backend/app/database/falkor/code-graph-backend/tests/index.py (1 hunks)

🧰 Additional context used

🧬 Code graph analysis (3)

backend/app/database/falkor/code-graph-backend/api/analyzers/source_analyzer.py (2)

backend/app/database/falkor/code-graph-backend/api/entities/entity.py (1)

• Entity (6-32)

backend/app/database/falkor/code-graph-backend/api/entities/file.py (1)

• File (7-36)

backend/app/database/falkor/code-graph-backend/api/analyzers/analyzer.py (2)

backend/app/database/falkor/code-graph-backend/api/entities/entity.py (1)

• Entity (6-32)

backend/app/database/falkor/code-graph-backend/api/entities/file.py (1)

• File (7-36)

backend/app/database/falkor/code-graph-backend/api/entities/file.py (1)

backend/app/database/falkor/code-graph-backend/api/entities/entity.py (1)

• Entity (6-32)

🔇 Additional comments (6)

backend/app/database/falkor/code-graph-backend/tests/index.py (1)

7-8: LGTM! Imports correctly converted to relative paths.

The conversion of Project and prefix_search imports to relative paths aligns with the PR objective and maintains consistency with other module imports.

backend/app/database/falkor/code-graph-backend/api/analyzers/analyzer.py (1)

5-6: LGTM! Relative imports correctly implemented.

The conversion from absolute imports (api.entities.*) to relative imports (..entities.*) is correct and aligns with the PR objective to standardize imports across the code-graph-backend package.

backend/app/database/falkor/code-graph-backend/api/analyzers/source_analyzer.py (1)

5-6: LGTM! Relative imports correctly implemented.

The conversion from absolute to relative imports matches the pattern used in other analyzer modules and correctly references the entities package.

backend/app/database/falkor/code-graph-backend/api/entities/file.py (1)

4-4: LGTM! Relative import correctly uses single dot for same-package import.

The conversion to a relative import using a single dot (.entity) is correct for importing from a sibling module within the same package and aligns with the PR objective.

backend/app/database/falkor/code-graph-backend/api/index.py (1)

9-16: LGTM! Comprehensive conversion to relative imports.

All imports have been correctly converted from absolute to relative paths using single-dot notation (.), which is appropriate since these are sibling modules within the api package. The changes are comprehensive and consistent across all submodule imports.

backend/app/database/falkor/code-graph-backend/api/entities/entity.py (1)

1-2: LGTM! Correct Python 3.10 compatibility fix.

Moving Self from typing to typing_extensions is the correct approach, as Self was only added to the standard typing module in Python 3.11 (PEP 673). For Python 3.10, the backport from typing_extensions (v4.0.0+) must be used instead.