Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate from Relative Imports to Absolute Imports #161

Open
deadaf opened this issue Jul 28, 2024 · 0 comments
Open

Migrate from Relative Imports to Absolute Imports #161

deadaf opened this issue Jul 28, 2024 · 0 comments
Labels
enhancement New feature or request priority:medium

Comments

@deadaf
Copy link
Member

deadaf commented Jul 28, 2024

Project currently uses relative imports in several places, which can lead to various issues such as difficulties in refactoring, reduced readability, and complications when running tests or deploying the project. To improve the maintainability and clarity of our codebase, we should transition to using absolute imports.

Proposed Solution:

  1. Identify all relative imports in the project.
  2. Replace relative imports with absolute imports.
  3. Test the project thoroughly to ensure that the changes do not introduce any bugs or issues.

Example:

Current Relative Import:

from .module import SomeClass

Proposed Absolute Import:

from quotient.module import SomeClass

Make PR to rewrite branch only.

@deadaf deadaf added enhancement New feature or request priority:medium labels Jul 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority:medium
Projects
None yet
Development

No branches or pull requests

1 participant