fix: resolve markdown field rendering issue #97
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes issue #49 by properly handling custom field types in InternationalizedField.
Changes
Problem
The issue was caused by the InternationalizedField component not properly preserving custom field components while applying internationalization features. This was preventing custom field types like markdown from rendering correctly.
Solution
This fix ensures that custom field types like markdown are rendered correctly while maintaining the plugin's internationalization functionality.