Repository navigation
Fix package-named module imports - #10
Conversation
Reviewer's GuideThe resolver now falls back to Flow diagram for single-file package module resolutionflowchart TD
A[Import package] --> B[Resolve package directory]
B --> C{main.fl exists?}
C -->|Yes| D[Use main.fl]
C -->|No| E{package/package.fl exists?}
E -->|Yes| F[Use package/package.fl]
E -->|No| G[Try existing flat package.fl fallback]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
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. Comment |
Sourcery withdrew this approval because it has stopped reviewing this pull request.
|
Sourcery has withdrawn its approval of this pull request. It auto-reviews a pull request 5 times, and this push is past that limit, so the approval no longer reflects code Sourcery has read. Comment |
Sourcery withdrew this approval because it has stopped reviewing this pull request.
|
Sourcery has withdrawn its approval of this pull request. It auto-reviews a pull request 5 times, and this push is past that limit, so the approval no longer reflects code Sourcery has read. Comment |
Fix bare-name imports for single-file modules named after their package. Add coverage for installed package resolution and document the supported layouts.