Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Proper error message using conan remote disable/enable if remote doesn't exist

See original GitHub issue

Using Conan 1.19 you will be able to enable or disable remotes with conan remote enable/disable remote_name. If the remote does not exist there is no error message. There should be one error message in this case.

To help us debug your issue please explain:

I’ve read the CONTRIBUTING guide.
I’ve specified the Conan version, operating system version and any tool that can be relevant.
I’ve explained the steps to reproduce the error or the motivation/use case of the question/suggestion.

Issue Analytics

State:
Created 4 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

Minimoniumcommented, Oct 1, 2019

From Slack’s discussion with @lasote it was decided that passing the output into Remotes would be unnecessarily complex. Up until there is an output refactor that would include work on the output verbosity - it’s better to leave it simple. Given that the current PR is sufficient. 🙂

0reactions

Minimoniumcommented, Sep 29, 2019

Note that in the current implementation the wildcard case does not throw an error if nothing was picked. 🙂

About the output, the Remotes class doesn’t have the output as an attribute. Is the right approach to pass it down as a function parameter? Wouldn’t it be too much? Or returning an output? Again, a bit wacky.