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.
`dotnet complete` behaves with `Contains` instead of `StartWith`
See original GitHub issueAfter following @timheuer’s instructions on how to set it up for my Powershell profile, I typed dotnet a→ and it displayed the following.
After upgrading from Preview 5 to Preview 7, the behavior still hasn’t changed. After reverse-engineering the script, I tried to reproduce the problem and it didn’t seem like anything could make it work.
Running dotnet --version:
5.0.100-preview.7.20366.6
Running dotnet --list-sdks:
3.1.100 [C:\Program Files\dotnet\sdk]
3.1.201 [C:\Program Files\dotnet\sdk]
3.1.400-preview-015151 [C:\Program Files\dotnet\sdk]
5.0.100-preview.7.20366.6 [C:\Program Files\dotnet\sdk]
I’m ready to jump onto a call if needed to retrieve the necessary bits and help the engineers understand why this is happening.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is indented to complete with contains. We’ve removed the dotnet migrate already. @sfoslund looks like it is a bug in completion. Could you help look into it?
Updating this issue. The behavior was that “add” should have been first and it wasn’t at the time.
It seems the code as since been updated to prioritize commands/parameters that starts with the chain of characters provided.
I consider this fixed and working.