Skip to content
This repository has been archived by the owner on Aug 16, 2020. It is now read-only.

The type definition of $loading in Nuxt.js conflicts with element-ui #18

Open
JohannesLichtenberger opened this issue Oct 7, 2019 · 8 comments

Comments

@JohannesLichtenberger
Copy link
Member

See: nuxt/typescript#49

I did the workaround locally mentioned in

nuxt/typescript#49 (comment)

However, I hope that gets fixed. Either from the Element-UI or Next.js developers...

@simhol
Copy link
Contributor

simhol commented Oct 7, 2019

I didn't check if there is an ongoing issue for this in the Element Repo. But I don't think it will be fixed by Nuxt

@JohannesLichtenberger
Copy link
Member Author

Yeah, it already has the wontfix label ;-)

@JohannesLichtenberger
Copy link
Member Author

Filed an issue, let's see: ElemeFE/element#17630

@pareshjoshi
Copy link
Contributor

But how do you workaround this? With latest sync, yarn build is now failing

@JohannesLichtenberger
Copy link
Member Author

Bad workaround I guess (changing the type to any): nuxt/typescript#49 (comment)

@JohannesLichtenberger
Copy link
Member Author

I hope it works for you, too? But it's for sure no real solution. For me as a Java and little bit Kotlin software engineer it's a bit strange to have such problems with name/type clashes.

@pareshjoshi
Copy link
Contributor

Yes, that worked. But the repo it in broken state, unless it is documented in readme file, no one will be able to figure it out

@JohannesLichtenberger
Copy link
Member Author

JohannesLichtenberger commented Oct 9, 2019

Yes, added to the README. However, I'm not sure if one of the projects will change anything :(

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants