You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, creating some events requires manual escape of illegal data. When I starting documenting writing methods (that attempts never was public) I found this issue and planned to fix it, but never had time to do that. We need to change creation API for these events to return an iterator over events instead of single event. Something like:
I'm using the
rss
crate in the crates.io codebase, which usesquick-xml
under the hood and for certain fields performs:According to https://en.wikipedia.org/wiki/CDATA#Nesting in a
CDATA
section]]>
needs to be encoded as]]]]><![CDATA[>
to not accidentally close theCDATA
section.When I'm using my test string (
"let's try & break this <item> ]]>, shall we?"
) however, I currently see this in the output:<![CDATA[let's try & break this <item> ]]>, shall we?]]>
Apologies if this was already reported, but I couldn't find a matching issue. Is the escaping of
]]>
the responsibility of the caller in this case?I noticed that the
BytesCData
documentation says:but that does not seem to be targeted at people using the library for serializing
CDATA
sections.Related:
]]>
inCDATA
is not escaped rust-syndication/rss#173The text was updated successfully, but these errors were encountered: