I’ve been changing the locale prop of the column “Discount” in my rich-table and now it keeps throwing invalid language tag.
All locales seem to be fine. Trying to remove the prop results in the editor freezing completely.
Update:
In my local code the culprit seems to be two backticks:
__composite[“14”][“locale”] = ``;
When i change it locally to a valid locale like de-DE it resolves the issue.
The problem however now is that there is no way for me to set this straight in plasmic,
as the editor keeps freezing when trying to change that specific locale…
Relevant links:
Hello @nathan_b I was unable to reproduce the issue, possibly because I don’t have access to your custom host. Can you share a screen recording of your issue?
Hi Sarah,
Thanks for your response.
I’ve recorded the issue, see video.
I first remove the locale from a random column, which works fine.
Then I try the same for the DISCOUNT columns.
As soon as I click it the the page freezes.
Hello @nathan_b Thank you for the screen recording. I have to be able to reproduce it to investigate further. I see the node focused in your screen recording is nested under custom code components that I do not have access to. Could you create a minimal reproducible project to verify if this is an issue with the Table component? Or possibly share the $ctx.fetchedData.items value that I can use directly (although that alone may not be enough to reproduce the issue on my end).
Hi Sarah,
The issue is not in any of my custom code components or my locally fetched data.
In the auto-generated Plasmic output for my page PlasmicDetails.tsx, a locale property is set to two backticks (``) which crashes my table component at runtime and prevents editing in the Plasmic editor (it freezes when I try to remove it).
If you would only be able to replace the two backticks on line 3253 with ”de-DE”, the issue should be resolved.
@nathan_b I attempted to manually fix your project bundle, although I can’t verify since your host appears to be down. Sorry for the delay, it was a bit tricky to track this down, but it should no longer possible to get to this state in the studio.
Hi Samuel,
Thanks!
I’ll confirm it and get back to you.
Don’t worry about the delay, it was easy to workaround.
Best,
Nathan