Skip to content

remove code that was using an non-existent export #21

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
Aug 21, 2023

Conversation

void-mAlex
Copy link
Contributor

avoid runtime error if that code was ever to be hit
since the commented out code this used to reference is using global lookups which have been deprecated, this seems like the correct change to make

closes #18

avoid runtime error if that code was ever to be hit
@void-mAlex
Copy link
Contributor Author

the test/type failures have nothing to do with this pr, what will it take to land these changes?
also ty vm @SergeAstapov for reviewing already

@aklkv
Copy link

aklkv commented Aug 21, 2023

@SergeAstapov any updates on this?

@SergeAstapov SergeAstapov merged commit 9d71c53 into emberjs:main Aug 21, 2023
@SergeAstapov
Copy link
Contributor

@aklkv looks good to me!

@mixonic woudl you be able to publish new patch version to npm as I don't have permissions?

davidtaylorhq added a commit to chancancode/discourse that referenced this pull request Sep 6, 2023
This turns 'missing export' warnings into errors, and will help us catch them in CI.

This commit also includes fixes for two such problems:

- Updates incorrect import in auth-complete.js

- Patches legacy-built-in-components with the change from emberjs/ember-legacy-built-in-components#21 (merged but not yet released)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Internal import of context from commented out export in components/_internals
3 participants