Add tests and documentation updates for StructBlock translatable_blocks support (based on #752) #882
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 adding comprehensive tests and documentation improvements for the already-implemented translatable_blocks feature on the open #752, which addresses issue #307.
The feature allows developers to control which sub-fields of a StructBlock are translatable by defining a translatable_blocks attribute on the block class.
The core implementation changes were introduced in the cherry-picked commits (6835d9d, 417b8de, 91ad754, 0205300) from the @freddiemixell's fork.
The tests ensure the feature works as designed and the documentation provides clear guidance for developers on how to use translatable_blocks to control which StructBlock sub-fields are translatable, addressing the long-standing request in issue #307.
Closes #752.
CC: @freddiemixell (?) @zerolab for review. Appreciate any feedback!