How is changing the tests a fix?

How is changing the tests a fix?

Maybe I misunderstood:

• Test suite is failing with Vegafusion 2 #3701 (comment)
• Test suite is failing with Vegafusion 2 #3701 (comment)
• Test suite is failing with Vegafusion 2 #3701 (comment)

But my opinion in (#3701 (comment))

I'm torn on whether to make all date parsing a little less efficient by always checking for this as a special case (with a \d{4} regular expression) in VegaFusion. It's not a hard fix for our tests, and I can mark it prominently as a breaking change with instructions in the VegaFusion and Altair 5 changelogs. Open to suggestions.

@jonmmease IMO I don't think these should be interpreted as dates without a format specifier.

A 4 digit number (string?) is so ambiguous

@mattijn I'm happy to revert the examples, if @jonmmease is fixing on the rust-side

• 141182a (#3702)
• 2e05ec2 (#3702)

Better not change the encoding of these examples. This will change the appearance of the charts. This are real altair examples as are seen in the documentation. Maybe we can skip these examples with the reported issue when doing vegafusion related tests for now.

Better not change the encoding of these examples. This will change the appearance of the charts. This are real altair examples as are seen in the documentation. Maybe we can skip these examples with the reported issue when doing vegafusion related tests for now.

@mattijn I've used an xfail on these instead of a skip

If the issue does get resolved upstream - we can find out by them emitting an xpassed

Not sure what the title should be for this PR

Edit: thanks @mattijn 😃