Uh oh!
There was an error while loading. Please reload this page.
Implement Lingo translation registry - #1
Merged
Merged
Conversation
zekageri
marked this pull request as ready for review
August 12, 2026 16:25
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
{language, key enum type}pairget()/find()lookup with same-domain default-language fallbackpreferPsram = trueby default, using PSRAM first and normal 8-bit heap as fallbackPSRAM behavior
Lingo mirrors the PSRAM preference used by other ZekStack libraries such as Seal. During
init()it allocates the bounded table registry withMALLOC_CAP_SPIRAM | MALLOC_CAP_8BITwhen PSRAM is available andpreferPsramis enabled. If that attempt fails, it falls back toMALLOC_CAP_8BIT. No lookup or table-registration operation allocates afterward.Dedicated host tests compile the ESP32 allocation path against a heap-caps stub and verify:
preferPsram = falsebypasses PSRAMAPI shape
The intended Core usage remains concise:
Different feature enums can reuse the same underlying numeric values without collisions.
Validation
Validated locally with:
GitHub CI additionally builds every example across ESP32, ESP32-S3, ESP32-C3, and ESP32-P4 and enforces the shared ZekStack clang-format configuration.