Closed Dynom closed 3 years ago
I don't really want to require users to manually escape values. go-ical should transparently do it.
Hi @emersion,
That'd be even better, but does this mean all values are now already escaped? So basically I don't need to apply any escaping to any value which is set on on a Prop
?
I wonder. What does the RFC ABNF say?
Your guess is as good as mine.
I've been reading up on it and I'm not sure on some accounts. e.g.: is a semicolon ;
allowed after a colon :
or does it need to be escaped? Currently in the go-ical implementation it isn't, I'm not sure if it should be. I'd love a reference implementation, but I'm not at that point yet, I had hoped you already had an answer on it :-)
Hi,
Prop.SetText()
applies value escaping throughProp.SetTextList()
. However it's currently too opinionated to use a general value escaping. I propose to open up the escaping, te be re-used for more complex situations:Now we need to duplicate the escaping functionality to make sure that the value passed here is also properly escaped. Ideally I would like to see an
ical.EscapeValue()
which does so that there can be consistent escaping.