aaubry / yamldotnet.editor Goto Github PK

I would like to be able to configure which extensions this plugin picks up, in my environment the YAML files are not with yml / yaml extensions (and cannot be sadly) so I cannot use it

Just installed 1.6.1 today.
Was editing a new YAML document in Visual Studio 2013 with Update 4.
Entered about 42 lines. Cannot include lines, but can say it had one key containing 6 list items each having six normal keys with string values. Nothing looked complicated or edge-case like.
Went to end of document to add new line.
Got popup error (below) that suggested I look in this:
C:\Users\ME\AppData\Roaming\Microsoft\VisualStudio\12.0\ActivityLog.xml

Found this error at bottom of activity log:

System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. Parameter name: span at Microsoft.VisualStudio.Text.SnapshotSpan..ctor(ITextSnapshot snapshot, Span span) at YamlDotNetEditor.ErrorTagger.CreateErrorTag(SnapshotSpan span, Token token, String type, String message) at YamlDotNetEditor.ErrorTagger.d__2.MoveNext() at Microsoft.VisualStudio.Text.Tagging.Implementation.TagAggregator`1.d__5.MoveNext()

I could ignore the error and continue.

It happens when there are comments in the .yml file. The issue happens on this line:

emitter.Emit(parser.Current);

...in this file https://github.com/aaubry/YamlDotNet.Editor/blob/master/YamlDotNetEditor/CommandHandlers/FormatDocumentCommandHandler.cs#L55

So the error happens in the YamlDotNet NuGet package somewhere that can't be fixed from the extension itself.

Repro steps

In a YAML file containing this:

# version format
version: 1.0.{build}

Now invoke the Format Document command (Ctrl+K+D) and you get the error.

I can send a PR that fixes this. It's a small change. Interested?

At the moment I can create e.g. a new XML File via the Visual Studio 2012 menu, but YAML doesn't seem to be available. Not sure if it's not implemented or not working.

FILE -> New File -> YAML File

I guess it's not the biggest deal, but just wanted to make you aware.

PS: thanks for supporting every modern version of Visual Studio.

Same as #19, but for VS 2019.

Unfortunately, the workaround there of downloading and running the install manually doesn't work for VS2019, so we won't have a way to install it until the package is updated.

Not sure if this is YAML syntax thing or not.

Hope there will be syntax highlight for sub-string like

Name: !Sub "${AnotherParameter}-sub-string"

It would be useful to be able to configure settings like indentation and associated file extensions. I don't know how this can be done, but maybe someone knows?

Consider the Yaml block scalar below:

example: >2
  First line of text,
  end of text

Is it possible for YamlDotNet to pass the indentation indicator value of 2?

Indent with 2 spaces looks better to me than 4. So I really would like a configuration to alter that based on personal interest.

One good place to put it the configuration under Options > Text Editor > YAML, which seems to be standard place for indent config. But sadly, YAML doesn't have an entry there.

How hard would it be to adopt this plugin to Visual Studio 2010? Is there alternatives?

Please support vs 2017.

SaltStack uses yaml files extensively, however they use the .sls extension rather then .yaml. Would it be possible to support that extension as a valid yaml file?

I would suggest renaming the extension to YAML Editor. The name is a little cryptic right now and doesn't reflect very well what it is. Also, the description could be more flashy and say something like Provides a complete YAML editing experience in Visual Studio or something to that effect.

Have high quality images (see PR #8), naming and descriptions makes a huge difference for your download count.

Also, perhaps update the Gallery page with more screenshots and a list of features that your extension provides, including links to create issues and/or suggest features etc.

I just tried to update from 1.4.0 to 1.4.1 and received the same error as reported here madskristensen/WebEssentials2013#1751