Skip to content

fix: replace aliased import with unaliased import #17207

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

Merged
merged 1 commit into from
Apr 2, 2025

Conversation

bcpeinhardt
Copy link
Contributor

If you take a look at the comment above, these imports need to be unaliased.

@bcpeinhardt bcpeinhardt requested a review from code-asher April 2, 2025 00:29
@bcpeinhardt bcpeinhardt requested a review from stirby April 2, 2025 00:29
@bcpeinhardt bcpeinhardt changed the title fix: aliased import fix: replace aliased import with unaliased import Apr 2, 2025
@stirby
Copy link
Collaborator

stirby commented Apr 2, 2025

/cherry-pick release/2.21

@bpmct bpmct merged commit 51ce047 into main Apr 2, 2025
32 of 34 checks passed
@bpmct bpmct deleted the bcpeinhardt/fix-aliased-import branch April 2, 2025 01:27
Copy link

Cherry-pick failed with Merge error 51ce04780d79b3d9616815b2c52a9e5f8b9192e6 into temp-cherry-pick-e86291-release/2.21

@github-actions github-actions bot locked and limited conversation to collaborators Apr 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants