-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat: Diagnose unresolved field, method call and call expression #14243
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
Conversation
Veykril
commented
Mar 3, 2023
•
edited
Loading
edited
@bors r+ |
☀️ Test successful - checks-actions |
You can put |
Hey all, I don't know if this helps but I'm seeing an unresolved-field error on a field that definitely exists and compiles just fine. I think the problem is actually the weird dependencies I've introduced into my workspace modules though. I've reproduced it here: https://github.com/martijnarts/ra-unresolved-field-repro Do you want me to create a new issue for this, or maybe add to the Diesel issue? Here's what it looks like when breaking: |
That looks like an interesting issue (with a nice preproduction). Could you open that as a new issue? |
Created here: #14296 |