Psych::DisallowedClass during some locale files convertion to js

[dsawa]

Hey,

I have recently updated React on Rails to the latest (6.9.3) and updated webpack to v2 (along with all configurations). However one thing changed that breaks my current project.

I get

Psych::DisallowedClass: Tried to load unspecified class: Symbol

every time I for example run rake commands (impossible to run migrations).

During investigation I managed to find a simple solution. Problem occurs in LocaleToJs.

If I change YAML.safe_load to just YAML.load it works. I could make a new PR with this small change, but I see that it was changed for some reason in PR that updated whole React on Rails to support webpack 2. What's the reason?

It can be pain in the ass when relying on different locale files from different gems that you not necesarrly can control. In my example, origins of the problem are from spree_i18n gem (FR translations).

Should I make PR with change to YAML.load ?

[justin808]

@dsawa here's a discussion of the issue: ruby/psych#119

I need some more details on why this fails. I'm guessing that there's something odd about your translation files using symbols for values rather than strings.

It's 100% clear that YAML.safe_load was added so that if don't want arbitrary objects, then so be it.

Why would you have a symbol?

CC: @JasonYCHuang

[justin808]

@dsawa is this still an issue?

[ilyamkin]

Same issue here.

UPD:
I made some workaround. These symbol locales were from other gem, so I moved my locales to locales/client and used the i18n_yml_dir property.
I think it's good to isolate translations. Can we add this property in react-webpack-rails-tutorial because I used all translations and configs from this project?

[dsawa]

@justin808 Yes it is. Like @ilya4544 said, and me before, it's not me that I have symbol or something in translations. Those locales come from other gem.

I'll try ilya4544 workaround later.

[justin808]

I'm open to a PR or reopening this discussion if needed.

[dimasjt]

I got the same issue, it's because the translation have symbol value, I use rails-i18n https://github.com/svenfuchs/rails-i18n/blob/master/rails/locale/zh-CN.yml#L59

[markopavlovic]

same issue here, sometimes you use symbols for date definitions

[AntonAL]

I had the same issue, found recent changes in my .yml file, that had used definitions like this:

formtastic:
    :yes: 'Да'

Changed :yes to yes like this,

formtastic:
    yes: 'Да'

and issues was disappeared.