Open jssblck opened 1 month ago
I think I have the same issue but just have not recognized it.
I use RustRover as my IDE so I do not get to see the Rust-Analyzer errors directly but I've never had code-completion/intellisense on my ApiDoc struct.
I'll have a look but my knowledge about the rust-analyzer is fairly limited. Would be great if someone else could also take a look at it.
I suspect that the issue here is that Rust Analyzer executes the macro in a different directory, so making the macro normalize the path to be based on the workspace root would fix the problem.
If I get time I'll take a stab at fixing it!
I suspect that the issue here is that Rust Analyzer executes the macro in a different directory, so making the macro normalize the path to be based on the workspace root would fix the problem.
If I get time I'll take a stab at fixing it!
This would be great 👌
Let me know if you need any help. Also if this isn't the root problem please report it back.
I've noticed the same issue but had no clue about how to fix it. Thanks for your help
Hello! Thanks for taking the time to make this library, it's great!
In #9, an issue was observed with "workspace usage". The decision was that this wasn't truly broken, which is fair, but a problem when the code interacts with Rust Analyzer.
Specifically, I have code like this:
This causes Rust Analyzer to report the error "Failed to parse file: ./server/src":
However, the build succeeds:
Obviously, this isn't a case where the library is broken, but I think this is a case where the library makes assumptions about how the macro is executed that aren't compatible with Rust Analyzer.
Do you have any suggestions for steps I could take to resolve this issue?