Version compatibility issue: Unable to write any cells under golang 1.21.0.

[zhengkai]

Description

This morning, after an automatic upgrade to 1.21.0, I noticed that excelize is unable to write any cells, even using the examples from the official readme. The sheets, however, appear to be functioning normally. There are no error messages during the usage of SetCellValue and SaveAs, but the cell contents remain blank.

I didn't make any code changes; I simply replaced go build with go1.20.7 build and everything returned to normal.

Environment details (OS, Microsoft Excel™ version, physical, etc.):
Ubuntu 22.04
LibreOffice 7.3.7.2
Intel 9700K

[xuri]

Thanks for your issue. This was similar with #1465, #1595. There are some incompatible changes in the Go 1.21 encoding/xml library. I have given feedback to the Go team and created a patch for it, and still waiting for a reply. Please apply the patchsets in the CL https://go.dev/cl/466295 if you can.

[xijaja]

I just found this problem too。

[fifsky]

Is it compatible with go1.21? It will be a long time before the official merger. Projects that rely on excelize will not be able to use go1.21

[Desuuuu]

Removing the XMLName field from struct types that are not expected to have an explicit namespace seems to be a solution.

https://go.dev/play/p/z-acRVzkk6G

That should work as long as the type is not marshaled directly and its usage in other structs has the proper xml tag.

[xuri]

Hi @fifsky. I'll consider revendoring Go encoding/xml package in 1.16.15 (for backward compatible) in github.com/xuri/xml this week.

[fifsky]

Hi @fifsky. I'll consider revendoring Go encoding/xml package in 1.16.5 (for backward compatible) in github.com/xuri/xml this week.

OK, thank you for your reply

[xuri]

Hi @fifsky, I noticed that the Go team has added golang/go#62051 to the Go1.21.1 milestone, so I suggest waiting for the next minor releases, and you can vendoring the Go encoding/xml package by yourself if you need to.

[xuri]

Removing the XMLName field from struct types that are not expected to have an explicit namespace seems to be a solution.

https://go.dev/play/p/z-acRVzkk6G

That should work as long as the type is not marshaled directly and its usage in other structs has the proper xml tag.

Yeah, but we also need to marshal sub-type structs variable directly (such as marshal type variable B to XML element <b></b> in the example), in this case, still need type B has the proper xml.Name tag.

[fifsky]

@xuri I noticed that, too, thanks