vcard4 chokes on maybe broken VALUE=UNKNOWN tag

[stefand]

Here's another example of apparently nextcloud created junk:

TEL;TYPE=CELL;VALUE=UNKNOWN:+01555123456

There's an open nextcloud bug about this: nextcloud/contacts#3578 . It would be nice if vcard4 gracefully ignores this tag when parsing with parse_loose(). I guess parse() should reject it though.

example3.txt

[stefand]

Probably the best thing to do would be to treat anything unknown as ValueType::Text in parse_loose() - afaics that should give the same result as if the VALUE= tag wasn't there.

[tmpfs]

Hey @stefand can you check if #23 fixes the problem for you please?

If so I will merge that PR!

[stefand]

Yes, it fixes the bug for me, thanks!

It seems that the recently released Nextcloud 30.0.8 stopped adding those tags when I edit a phone number. Maybe they fixed the bug too (although they didn't close it yet), or it needs more factors to trigger. Regardless I think its good to have your patch.

Can you push a new release to Cargo with those fixes?

[tmpfs]

Ah, glad they seem to have fixed the underlying problem!

I've published 0.7.2 with these fixes, cheers 👍