-
Notifications
You must be signed in to change notification settings - Fork 37
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 use types #1129
Fix use types #1129
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Estimated impact to a consuming app, depending on which bundle is imported
|
@MichalBryxi, would you like to review? |
@@ -10,7 +10,7 @@ export interface InternalFunctionResourceConfig<Value = unknown> { | |||
[INTERNAL]: true; | |||
} | |||
|
|||
export const CURRENT = Symbol('ember-resources::CURRENT'); | |||
export const CURRENT = Symbol('ember-resources::CURRENT') as unknown as 'CURRENT'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the fix: typescript has been annoying with symbols and inferred types lately. :(
Question: The test checks that Ember code works. But does that also prove that TS won't report problems? My example code compiled just fine. I was only getting squiggly line under respective TS code. Is that guaranteed because the TS checks on the testing source code would fail? |
Fix #1128
Issues:
CURRENT
symbol was exposed, and caused interface matching to fail -- it has been cast to a non-symbol via the same lies @runspired is using in ember-data 😅Unresolved:
use
apis