Skip to content
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

help: message: Type definition not found for Input identifier #45

Open
Vehmloewff opened this issue Jan 21, 2022 · 2 comments
Open

help: message: Type definition not found for Input identifier #45

Vehmloewff opened this issue Jan 21, 2022 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@Vehmloewff
Copy link

Vehmloewff commented Jan 21, 2022

I keep getting errors in vscode.

image

custom attribute panicked

help: message: Type definition not found for `Input` identifier

The project does, however, compile using deno_bindgen without errors.

@littledivy littledivy added the bug Something isn't working label Jan 23, 2022
@littledivy littledivy added this to the 0.5.0 milestone Jan 23, 2022
@littledivy littledivy modified the milestones: 0.5.0, 0.6.0 Feb 8, 2022
@felipetesc
Copy link

felipetesc commented Mar 12, 2022

I've the same issue with VSCode, and Sublime. The problem is being reported by rust-analyser and RLS on VS.
When I deactivate rust-analyser and activate RLS I get the same "error: custom attribute panicked"
To ilustrate :
https://www.reddit.com/r/rust/comments/t17vpj/rustanalyzer_and_procmacros/
https://stackoverflow.com/questions/70383686/rust-analyzer-throws-unresolved-macro-despite-disabling-macro-error-and-unr
https://zulip-archive.rust-lang.org/stream/185405-t-compiler/rust-analyzer/topic/Fail.20to.20find.20macro.20definition.20under.20VSCode.html

@1216892614
Copy link

So, would this be fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants