-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
upgrade 3.0.0-beta.2 to 3.0.0-beta.3 some file failed #3924
Comments
Thank you for opening this issue. In order to confirm it, we'll have to reproduce it. https://codesandbox.io/s/github/marmelab/react-admin/tree/next/examples/simple This is the simplest way to confirm a bug is related to the React Admin codebase. |
What does "../core did not have types should be" mean? When you mean "some files fail", what does actually fail, and what's the error message? also, you mention 2 separate versions in your description, which one are you using? |
I'm running into a similar issue when using a "legacy" dataProvider, it seems that the bug was introduced in dccc3cb, and since then this import is not resolving properly dccc3cb#diff-d2b6c4d5acf1bd4486f924173f33fc4cR11 I also noticed that this for me only happens in Here is a codesandbox illustrating the issue: https://codesandbox.io/s/optimistic-frog-mr8lf |
Thanks, I managed to reproduce the issue. I'm Investigating. |
fixed by #3927 |
tdeo thank you for reproduce it ,same error with me . |
@fzaninotto sorry , i did not provide a clear description.anyway ,thank your attention. |
|
no, you'll have to wait until it's published. |
What you were expecting:
upgrade react-admin to 3.0.0-beta.3 from beta.2.
What happened instead:
some file have problem :convertLegacyDataProvider.ts
Steps to reproduce:
yarn upgrade react-admin@3.0.0-beta.3
Related code:
../core did not export right path.
Environment
The text was updated successfully, but these errors were encountered: