VObject 3.0.0-alpha1 released

[Evert Pot]

Hi everyone,

By far the 'most popular' bug report SabreDAV has had, is a bug in the VObject parser related to escaping ; and ,.
The unfortunate truth was that it required a pretty big overhaul of the vobject lib in order to fix this.

So, for the past 3 weeks I've been working on exactly this, and the result is a new alpha version.

If this was a problem that affected you, I would love to hear if everything now works as expected.


Full change list and BC breaks
------------------------------

A lot of stuff has changed, and even more features have been added that make it simpler to read and
manipulate these files.

Full list can be found here:

https://github.com/fruux/sabre-vobject/blob/master/doc/MigratingFrom2to3.md


What I would love to hear
-------------------------

* Are all your previous problems solved?
* Did you find anything complicated or annoying?
* Is there any other syntax sugar you can think of that will further improve this.

Once I officially release 3.0, I won't have the liberty to make API changes, so I'll be stuck here
for some time. If you're a VObject user, your feedback will help to make sure that we're not stuck
with an ugly library for several years.

Please give your feedback as a GitHub issue, here:

https://github.com/fruux/sabre-vobject/issues/new


Integration into SabreDAV
-------------------------

At the moment this library is not compatible with any sabredav version. So if you want to test it,
make sure you test this independently from sabredav.

SabreDAV 1.9 will integrate VObject 3 by default.
SabreDAV 1.7 and 1.8 will continue to run VObject 2.

However, I will make several changes in VObject 2 so that the API is more similar.
The end-goals is that even though SabreDAV 1.7 and 1.8 will ship with 2, you can
swap it out for version 3.

Installing
----------

You can install the alpha by downloading it:

https://github.com/fruux/sabre-vobject/archive/3.0.0-alpha1.tar.gz

Or by creating this composer.json file:

{
"require" : {
"sabre/vobject" : "3.0.0-alpha1"
}
}


Cheers,
Evert

[Thomas Tanghus]

On Tuesday 21 May 2013 20:11 Evert Pot wrote:
> By far the 'most popular' bug report SabreDAV has had, is a bug in the
> VObject parser related to escaping ; and ,. The unfortunate truth was that
> it required a pretty big overhaul of the vobject lib in order to fix this.

And it's looking pretty sweet :)

As for https://github.com/fruux/sabre-vobject/blob/master/doc/MigratingFrom2to3.md#rfc6868-is-used-to-serialize-parameters

How do common clients deal with parameters escaped with carets?

--
Med venlig hilsen,

Thomas Tanghus

[Evert Pot]

On May 22, 2013, at 6:01 AM, Thomas Tanghus <tan...@gmail.com> wrote:

> On Tuesday 21 May 2013 20:11 Evert Pot wrote:
>> By far the 'most popular' bug report SabreDAV has had, is a bug in the
>> VObject parser related to escaping ; and ,. The unfortunate truth was that
>> it required a pretty big overhaul of the vobject lib in order to fix this.
>
> And it's looking pretty sweet :)

Great!

>
> As for https://github.com/fruux/sabre-vobject/blob/master/doc/MigratingFrom2to3.md#rfc6868-is-used-to-serialize-parameters
>
> How do common clients deal with parameters escaped with carets?

Clients will just show the extra carets. But note that embedding a " or newline was technically not even allowed in parameters, so the only case where this will look 'weird', is clients that didn't follow the spec to the letter, or cases where users wanted to use a literal ^ somewhere (it will now look like ^^).

So I don't think many people will be affected by that.

Evert