xembly
xembly copied to clipboard
yegor256
Xembler.xml() doesn't have an option to omit the header
Xembly doesn't allow to generate xml fragment without the header <?xml version="1.0" encoding="UTF-8"?>.
It would be great to add a new method Xembler.xml(boolean header)
@dmzaytsev I think it's better to just build an XML without header by default. If someone will need a header, he/she can add it later, just by string concatenation. Agreed?
@yegor256 maybe to add the constant to Xembly in this case?
e.g. Xembly.HEADER
public final String HEADER ="<?xml version="1.0" encoding="UTF-8"?>"
@dmzaytsev well, some users may need XML 1.1 or a different encoding or a standalone attribute there.. I would rather leave it all to the user
@dmzaytsev thanks a lot for reporting, 15 mins added to your acc, pmt ID 58643900
@davvd Was this implemented ? Any relevant documentation would be great.
@0crat in (here)
@carlosmiranda Thanks for your contribution, @dmzaytsev/z! If you would be a member of the project, you would now earn +15 reputation points, as explained in §29. You can join and apply to it, see §2.
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
Xml without header
<a/>
May be stored as
{
"a": {
"-self-closing": "true"
},
"#omit-xml-declaration": "yes"
}
https://xmltojson.github.io/
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)
@carlosmiranda/z everybody who has role DEV is banned at #64; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)