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

Fix compat again #508

Merged
merged 1 commit into from
Dec 27, 2024
Merged

Fix compat again #508

merged 1 commit into from
Dec 27, 2024

Conversation

kageurufu
Copy link
Member

iamnotahippie reported breakage in HappyHare after PR #490 was merged. I did a bunch of investigation, and found that the path rewrite in the import aliasing was causing the imported modules to have the wrong internal package name, which caused subsequent relative imports to also look in the wrong place

This change fixes that, and with compat in place HappyHare now passes our --import-test

_Enter a good description of whats being changed and WHY

Checklist

  • pr title makes sense
  • squashed to 1 commit
  • added a test case if possible
  • if new feature, added to the readme
  • ci is happy and green

iamnotahippie reported breakage in HappyHare after PR #490 was merged.
I did a bunch of investigation, and found that the `path` rewrite in the
import aliasing was causing the imported modules to have the wrong
internal package name, which caused subsequent relative imports to also
look in the wrong place

This change fixes that, and with compat in place HappyHare now passes
our `--import-test`
@kageurufu kageurufu requested a review from a team as a code owner December 24, 2024 18:42
@rogerlz rogerlz merged commit 1a4c40f into main Dec 27, 2024
2 checks passed
@rogerlz rogerlz deleted the fix_compat_again branch December 27, 2024 13:27
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.

2 participants