Error on proc macro

[aurexav]

It can work 2 days ago.

But today I update it on vscode.

And the proc macro report error. Looks so noisy.

[aurexav]

This macro is from crate frame-support.

frame-support = { version = "2.0.0" }

use frame_support::decl_storage;

[bjorn3]

It expects CARGO_PKG_NAME to be set: https://github.com/paritytech/substrate/blob/918313f9bea2766bddcef8ea5b5a454486f3acfe/frame/support/procedural/tools/src/lib.rs#L41

[aurexav]

It expects CARGO_PKG_NAME to be set: https://github.com/paritytech/substrate/blob/918313f9bea2766bddcef8ea5b5a454486f3acfe/frame/support/procedural/tools/src/lib.rs#L41

Any quick fix that I can do?

Seems there's a env setting in rust-analyzer.

[flodiebold]

The macro-error diagnostic is new; this was probably already not working before you updated, you just didn't see the error. You can disable the macro-error diagnostic using the rust-analyzer.diagnostics.disable setting to go back to not seeing it ;)

Setting CARGO_PKG_NAME would probably have to be done programmatically by RA, since it depends on the crate we're "compiling", I guess? I wonder if that's intended/supported usage though...

[aurexav]

The macro-error diagnostic is new; this was probably already not working before you updated, you just didn't see the error. You can disable the macro-error diagnostic using the rust-analyzer.diagnostics.disable setting to go back to not seeing it ;)

Setting CARGO_PKG_NAME would probably have to be done programmatically by RA, since it depends on the crate we're "compiling", I guess? I wonder if that's intended/supported usage though...

Seems this setting not exist.

Oh, I found it.

"rust-analyzer.diagnostics.enable": false,

[tomjakubowski]

@AurevoirXavier I used this:

"rust-analyzer.diagnostics.disabled": [
  "macro-error"
]

Setting what you did disables all of rust-analyzer's diagnostics, probably not what we want.

[aurexav]

@AurevoirXavier I used this:

"rust-analyzer.diagnostics.disabled": [
  "macro-error"
]

Setting what you did disables all of rust-analyzer's diagnostics, probably not what we want.

Thanks.

[ntn-x2]

The same is happening again, on Mac Silicon with Rust Analyzer version 0.2.853 and VSCode version Version: 1.63.2
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3, for the frame macro frame_support::pallet. Anyone else with the same issue and, more importantly, anyone with a fix? 😂

Diagnostics for macro-error are already disabled, but when then exporting the module wrapped by the macro, it is an unresolved import error. Enabling the diagnostics results in the very same problem as discussed above.