DEPRECATION WARNING: Using a 'Essence#{type}' content is deprecated. Please use a '#{type}' instead #2411
Replies: 10 comments
-
Have you tried using - name: icon_link
ingredients:
- name: some-thing
type: Text instead of - name: icon_link
contents:
- name: some-thing
type: EssenceText in your
We still support both, but ingredients is the future. Hence the deprecation warnings. |
Beta Was this translation helpful? Give feedback.
-
When I try switching from Things like
And I can't access those classes myself in a console either. |
Beta Was this translation helpful? Give feedback.
-
The classes are all namespaced to You need to run a task to convert the existing elements to ingredients:
|
Beta Was this translation helpful? Give feedback.
-
Is there a built-in way to migrate |
Beta Was this translation helpful? Give feedback.
-
Yes, the above mentioned task |
Beta Was this translation helpful? Give feedback.
-
Do I need to change something in my I tried changing |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Sorry, you also need to change Then run the task. Some background in this change can be found in this PR #2061 (comment) We really need to update the guides... |
Beta Was this translation helpful? Give feedback.
-
Ok, that worked. Could I drop the "alchemy_essence_#{type}" tables from the database now? |
Beta Was this translation helpful? Give feedback.
-
Since the Models are loaded in production and Rails would fail without the tables, I would not recommend that. They do no harm. |
Beta Was this translation helpful? Give feedback.
-
Here's a small sample of my server log:
Not only do these a totally pollute my logs, The suggested fix doesn't exist yet. The schema is all
Essence#{type}
tables.I see
Alchemy::Deprecation.silence
but it takes a block and I don't want to pass my entire app into that block.What's my recommended fix here?
Beta Was this translation helpful? Give feedback.
All reactions