Jon Sequeira
Jon Sequeira
@marckruzik, this is a very good suggestion and I think it's fine to discuss here. The syntax would need to be a little different from your example, I think, since...
These are all good suggestions and more readable that what I've sketched so far, which looks like this: ``` #!test @input:"Please enter a value for blah",save,type=file,name=blah ``` What's driving this...
> Do you have an example of multiple inputs in a single magic command? Take a look at #3194. The idea would be that when there are multiple inputs in...
> I just found https://github.com/dotnet/command-line-api/issues/37#issuecomment-574879829 talking about the issue. System.CommandLine's custom parse delegates solved this issue. But the ability to have whitespace not be treated as a delimiter between arguments/options...
Another possibility would be to support directly inlining JSON into the magic command in these cases: ``` @input:{ "prompt":"please enter a filename", "default":"readme.txt", "type":"file", "save": true } ```
I'm not able to reproduce this issue and I don't think it would be an issue with .NET Interactive since it uses whatever NuGet configurations you have on your machine....
If you run `dotnet nuget list source` in the same directory where the notebook is located, what do you see?
.NET 8 support was released today. Please update and let us know if it resolves the issue.
@princeanire, this is unrelated. The cancel button will not cancel infinite loops, since .NET Core / .NET 5 / .NET 6 did not support an equivalent of .NET Framework's `Thread.Abort`....