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
Digging into this a bit further and experimenting with it, it looks like there are 2 potential issues we're going to run into with this
The first is that attributes are lost when deserializing then reserializing, the attributes are turned into normal tags which would break the jfc schema. [1]
The second issue is that it doesn't support cases where there is an attribute and later a tag with the same name. This occurs in the JFC templates where the setting tag has an attribute 'control' and there is a separate 'control' tag later on. [2]
Good findings, thanks. It's unfortunate but I think your conclusion that we need to keep the dependency is correct, or else we can't do any validations or transformations on .jfcs.
JSoup is used for some light processing of
.jfc
XML documents. Unfortunately, we also expose the JSoupDocument
class as part of our own public API.Document
type should be abstracted away so that any library used for processing XML is an internal implementation detail of this libraryThe text was updated successfully, but these errors were encountered: