[Bug]: encode json data on column causing issue

[Mohammudullah]

Is the bug applicable and reproducable to the latest version of the package and hasn't it been reported before?

• Yes, it's still reproducable

What version of Laravel Excel are you using?

3.1

What version of Laravel are you using?

10.47.0

What version of PHP are you using?

8.3

Describe your issue

This json structured column {"en":"{\"en\":null,\"bn\":null,\"af\":null,\"bm\":null}","bn":null,"af":null,"bm":null} is affecting other next columns with it's own value

How can the issue be reproduced?

using this same json data on a column {"en":"{\"en\":null,\"bn\":null,\"af\":null,\"bm\":null}","bn":null,"af":null,"bm":null}. This will replace other columns data with it's value

What should be the expected behaviour?

the column should not spread to other columns.

[patrickbrouwers]

Can you explain a bit more what you are trying to do? Are you importing or exporting?
The json decode on export is just a fallback to make clear that something needs to be manually formatted.

[Mohammudullah]

I'm importing the data from csv. If you can see the image The 'type, price, tag, sku' should contain other columns data from csv. But it's containing 'description' column data

[patrickbrouwers]

Sounds like you didn't properly escaped the " enclosure in the CSV. The package will see the " and use it as an enclosure.

[Mohammudullah]

Sounds like you didn't properly escaped the " enclosure in the CSV. The package will see the " and use it as an enclosure.

I can understand that Json structure is not valid. But this data is coming from user. if they somehow mess with this "" enclosure. that csv will not work anymore. I handled invalid Json in my backend with null. so, If csv import can send me what data user entered, I can handle it on backend.