yaml Work Item Rss Feed

Closed Issue: Syntax highlighting conflicts with custom colors [7292]

yoav — Thu, 16 May 2013 09:12:34 GMT

The syntax highlighting should provide custom color classes as described in http://msdn.microsoft.com/en-us/library/bb165041.aspx (I'm assuming you use Managed Package Framework rather than Babel).

I use a custom color setup with light orange text on dark green to reduce eye-strain and allow a greater range of highlighting (since the text is light, different colors at the same brightness are much easier to distingush).

Commented Issue: Yaml parser cannot handle comments [14972]

mas912 — Mon, 02 Apr 2012 18:09:08 GMT

'K1': V1 # comment
K2: 'V2' # not comment
'K3': 'V3' # again not comment and "Error 1 Expecting mapping key (YA112)", because line 2 is broken
Comments: ** Comment from web user: mas912 **

Yes.

Commented Issue: Yaml parser cannot handle comments [14972]

BurtHarris — Mon, 02 Apr 2012 17:39:25 GMT

'K1': V1 # comment
K2: 'V2' # not comment
'K3': 'V3' # again not comment and "Error 1 Expecting mapping key (YA112)", because line 2 is broken
Comments: ** Comment from web user: BurtHarris **

I'm assuming the text under description represents the YAML file that's generating the problem for you, right?

Created Issue: Yaml parser cannot handle comments [14972]

mas912 — Fri, 30 Mar 2012 12:17:23 GMT

'K1': V1 # comment
K2: 'V2' # not comment
'K3': 'V3' # again not comment and "Error 1 Expecting mapping key (YA112)", because line 2 is broken

Created Issue: Tag related test failures [14164]

BurtHarris — Tue, 30 Aug 2011 09:52:03 GMT

When I check in the Load update this evening, there will be 9 tests failing.   Most of them (if not all) are related to the new Tag structure and how YAML tag properties are getting parsed.   Have at them...
A bunch are based on example from the Yaml 1.2 spec.   Y12_06_21, Y12_06_24, Y12_06_18, Y12_06_26, and Y12_08_21. These failures probably have a common root cause.
InEquality - probably a bug in the test
NoLiteral - Haven't investaged

Workitem9840 and Workitem9817 have their own bugs.   You're welcome to try to tackle them too.

Commented Issue: Tags containing a # [9817]

BurtHarris — Tue, 30 Aug 2011 04:22:15 GMT

Getting YA308 on tags containing a fragment (embedded #)
Comments: Perhaps it mutated, its now generating a YA308 not a YA309. I'm going to complete the refactoring of Loader before assigning.

Commented Issue: Tags containing a # [9817]

BurtHarris — Tue, 30 Aug 2011 04:02:20 GMT

Getting YA309 on tags containing a fragment (embedded #)
Comments: Adding a unit test for this in YamlBasicsTest.cs.

Closed Issue: CA1502 : AvoidExcessiveComplexity in Emitter.cs consturctor [13107]

BurtHarris — Tue, 30 Aug 2011 03:54:17 GMT

Comments: Emitter class no lonter exists.

Closed Issue: Unit tests fail in Debug Build [14089]

BurtHarris — Tue, 30 Aug 2011 03:48:44 GMT

The CoreUnitTest module has 56 tests that fail when run under the Debug build.

This appears to have something to do with the code contracts "rewriter" not adding required information to the assembly before running the test. Error messages look something like this, with reference to $evaluatingInvariant$ being the tipoff it has something to do with the code contracts rewriter.

Test method YaTools.Yaml.UnitTests.Y12ExamplesAuto.Y12_05_12 threw exception:
System.MissingFieldException: Field not found: 'YaTools.Yaml.YamlParser.$evaluatingInvariant$'.

Note: No longer happens. I don't know what I did to fix this. There are two tests currently failing, but they are related to issues I recently introduced around serialization (class Dump) and tagging of dump output.
Comments: Confirmed this no longer happens, under either debug or release builds.

Commented Issue: Unit tests fail in Debug Build [14089]

BurtHarris — Tue, 30 Aug 2011 03:43:30 GMT

Ryan says this is not reproducing.

Closed Issue: Test Warning: conflict during test run deployment [14091]

BurtHarris — Sun, 14 Aug 2011 21:31:54 GMT

Warning 8/14/2011 2:17:54 PM Warning: conflict during test run deployment: deployment item 'CoreUnitTest\Other\' specified by the test 'YaTools.Yaml.UnitTests.TaggedObjectSinkTest.Example2_12' cannot be deployed to 'Gentests.ps1' because otherwise the file 'C:\codeplex\Yaml\CoreUnitTest\Other\Gentests.ps1' would overwrite deployment item 'CoreUnitTest\Yaml_1.2\' specified by the test settings. MARZ
Comments: Resolved with changeset 82047.

Closed Task: Change core from .NET 3.5 depenent to .NET 2.0 dependent [14092]

BurtHarris — Sun, 14 Aug 2011 21:31:53 GMT

Comments: Resolved with changeset 82047.

Created Task: Change core from .NET 3.5 depenent to .NET 2.0 dependent [14092]

BurtHarris — Sun, 14 Aug 2011 21:29:06 GMT

Created Issue: Test Warning: conflict during test run deployment [14091]

BurtHarris — Sun, 14 Aug 2011 21:21:12 GMT

Commented Task: Decouple from DLR features that didn't make it into .NET 4.0 [14013]

BurtHarris — Sun, 14 Aug 2011 20:55:48 GMT

Comments: Associated with changeset 82046.

Closed Task: Separate build for .NET 2.x and 4.x based releases [14009]

BurtHarris — Sun, 14 Aug 2011 20:55:48 GMT

We will need to support a .NET 2.x compatable version for some time to come.    I put some effort into trying to have a single .csproj support both 2.x and 4.x versions following some patterns the DLR folks used, but I think that's too complex.   Instead we should setup seperate .csproj files to build the two variants.

How will the two variants be distinguished from each other?   Filename? Assembly version?

Should they both build from (mostly) the same sources, just with seperate references, or should we branch the source code.   I think I'd prefer not maintaining two seperate branches.

Related will be the question of how to deal with VS200x and VS 201x editor extensions, which will probably differ even more than the core language support.
Comments: Resolved with changeset 82046.

Closed Issue: .NET 4.0 Support [14008]

BurtHarris — Sun, 14 Aug 2011 20:55:47 GMT

Comments: Resolved with changeset 82046.

Closed Issue: Source Control Bindings in sln and csproj files. [6889]

BurtHarris — Sun, 14 Aug 2011 20:55:47 GMT

These bindings cause VS clients with the Source Gear Vault client to fail when attempting to load the csproj files in the solution. If the bindings are removed manually the projects load fine. It is unclear to me if this is defect in the settings I have locally, a problem with VS or with the vault client. An easy, if inconvenient for those not using svn, solution is to unbind these files in VS and keep the sln and csproj files ignorant of the source control provider. I will continue to see if I can find a work around in VS or the Source Gear Client.
Comments: Resolved with changeset 82046.

Created Issue: Unit tests fail in Debug Build [14089]

BurtHarris — Sun, 14 Aug 2011 20:50:00 GMT

The CoreUnitTest module has 56 tests that fail when run under the Debug build.

This appears to have something to do with the code contracts "rewriter" not adding required information to the assembly before running the test. Error messages look something like this, with reference to $evaluatingInvariant$ being the tipoff it has something to do with the code contracts rewriter.

Test method YaTools.Yaml.UnitTests.Y12ExamplesAuto.Y12_05_12 threw exception:
System.MissingFieldException: Field not found: 'YaTools.Yaml.YamlParser.$evaluatingInvariant$'.
Comments: Test method YaTools.Yaml.UnitTests.Y12ExamplesAuto.Y12_05_12 threw exception:
System.MissingFieldException: Field not found: 'YaTools.Yaml.YamlParser.$evaluatingInvariant$'.

Commented Task: Separate build for .NET 2.x and 4.x based releases [14009]

BurtHarris — Sat, 30 Jul 2011 16:04:27 GMT

NuGet seems to include several packages that tackle this sort of issue, consider following that pattern. For eample, the NuGet packaging of Newtonsoft.Json clearly is setup to support net 2.0, net 3.5, and net 4.0.