Make namespace optional for @XmlSerialName
See original GitHub issueIn a code like this:
@XmlSerialName("first", "", "")
override var first: GDMLRef<GDMLSolid>,
regular @SerialName
annotation does not work for some reason (it uses GDMLRef
as tag name instead of first
), so I have to use @XMLSerialName
, but writing empty strings each time is annoying. I think that additional arguments could be made optional.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
c# - Can I make XmlSerializer ignore the namespace on ...
Yes, you can tell the XmlSerializer to ignore namespaces during de-serialization. Define an XmlTextReader that ignores namespaces. Like so:
Read more >How to have optional attributes with xml - MSDN
I would like to have something like [OptionalField] and [OnDeserialization] ( available in C# ), but they don't seems to be provided in...
Read more >Specifying Namespaces for Elements and Attributes
XML elements and attributes can belong to different namespaces, and the XML Schema specification provides for multiple ... These attributes are optional.
Read more >Support for deserializing XML with namespace prefixes #63
Hello, I'm currently trying to use Jackson XML to serialize and deserialize XML with namespace prefixes - for example: x y I'm able...
Read more >xmlutil XML Serialization library for Kotlin ... - codeKK
Ideally integration with a well-developed native library as an option would be ... It will also make a best effort attempt at retaining...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This feature somewhat works. There seems to be an incremental compilation/caching issue (or something like that), but the library supports it now (when the compiler plugin cooperates).
Default arguments should now be supported in kotlin master/1.5.30-pre (see https://github.com/JetBrains/kotlin/commit/229085f3d13b09f87bc5421ec4e3f4272a78fabc ). When that is released I will revisit.