Bug: Decode stored data into array

[bogdancondorachi]

Hi there, thanks for the input!

Your client-side Panel translation code wasn't working for me, since the table field doesn't decode the stored data from string to an array. The YAML-encoded data from the content file is passed to the Panel as a string:

- 
  - ""
  - ""
  - ""
- 
  - This is column 1 in row 1
  - This is column 2 in row 1
  - This is column 3 in row 1

I have added a future-proof implementation. If the table field will decode the YAML to an array, the plugin will handle it accordingly.

Originally posted by @johannschopplich in #17

[johannschopplich]

I wasn't aware it's a bug. 🙂 Thanks!

[johannschopplich]

For reference, here's what I did:

• Check window.panel.content.version("changes")
• The data is identical to the serialized one in the model's content. I was ecpecting it to be decoded with Data::decode($obj, 'yaml'), just like blocks or other fields are deserialized for the Panel.

[bogdancondorachi]

Thanks for the input @johannschopplich, I'll see what I can do as it's something I've avoided since the start 😄. I'm guessing that's why I got reactive issues #20 on multilingual as well.

[johannschopplich]

No worries, I have a good workaround for now!