GithubHelp home page GithubHelp logo

Comments (9)

utkarshgupta137 avatar utkarshgupta137 commented on June 18, 2024 1

Can confirm that is fixed, thanks.

from crates.nvim.

Saecki avatar Saecki commented on June 18, 2024

Is the crate published on crates.io? Otherwise crates.nvim won't be able to retrieve metadata, since parsing a manifest located at a path is not supported (yet?).

from crates.nvim.

Saecki avatar Saecki commented on June 18, 2024

Also in this example the crates defined in the workspace Cargo.toml aren't the same as the ones used by the members.

from crates.nvim.

utkarshgupta137 avatar utkarshgupta137 commented on June 18, 2024

Also in this example the crates defined in the workspace Cargo.toml aren't the same as the ones used by the members.

You're right. I've fixed my comment & the problem is still occurring.

Is the crate published on crates.io? Otherwise crates.nvim won't be able to retrieve metadata, since parsing a manifest located at a path is not supported (yet?).

That is fine. It doesn't make much sense to manage versions of local dependencies anyway. But the Error fetching crate is very annoying. If there is a way to detect if the crate is local, then we can stop showing the error for them.

from crates.nvim.

Saecki avatar Saecki commented on June 18, 2024

Yes that should be possible, currently if there is a version specified crates.nvim tries to fetch metadata from crates.io. We could let this fail silently if a path or git url is specified.

from crates.nvim.

Saecki avatar Saecki commented on June 18, 2024

For that to work there would have to be proper workspace support, so that we could actually find the referenced workspace dependency.

from crates.nvim.

utkarshgupta137 avatar utkarshgupta137 commented on June 18, 2024

I've added a complete failing example in my fork.
I don't much care about workspace support. I imagine most mono repos have some way of managing workspace dependencies as we do. I would be happy enough to have the error stop popping up. It's very annoying because it stays after the file is closed & all the parent folders are marked with an x in NeoTree.

from crates.nvim.

aldanor avatar aldanor commented on June 18, 2024

+1 to this, enabling features in local crates results in annoying errors that don't go away.

from crates.nvim.

utkarshgupta137 avatar utkarshgupta137 commented on June 18, 2024

It would be nice if this crate could at least remove the diagnostics when the buffer is closed. Right now I use this shortcut: map("n", "<leader>nr", vim.diagnostic.reset, { desc = "Reset Diagnostics" })

from crates.nvim.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.