Skip to content

[Fixes #13800] Refact metadata i18n mechanism#13801

Merged
etj merged 3 commits intomasterfrom
13800_i18n_refact
Dec 10, 2025
Merged

[Fixes #13800] Refact metadata i18n mechanism#13801
etj merged 3 commits intomasterfrom
13800_i18n_refact

Conversation

@etj
Copy link
Contributor

@etj etj commented Dec 9, 2025

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

For all pull requests:

  • Confirm you have read the contribution guidelines
  • You have sent a Contribution Licence Agreement (CLA) as necessary (not required for small changes, e.g., fixing typos in the documentation)
  • Make sure the first PR targets the master branch, eventual backports will be managed later. This can be ignored if the PR is fixing an issue that only happens in a specific branch, but not in newer ones.

The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):

  • There is a ticket in https://github.com/GeoNode/geonode/issues describing the issue/improvement/feature (a notable exemption is, changes not visible to end-users)
  • The issue connected to the PR must have Labels and Milestone assigned
  • PR for bug fixes and small new features are presented as a single commit
  • PR title must be in the form "[Fixes #<issue_number>] Title of the PR"
  • New unit tests have been added covering the changes, unless there is an explanation on why the tests are not necessary/implemented

Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.

@etj etj self-assigned this Dec 9, 2025
@cla-bot cla-bot bot added the cla-signed CLA Bot: community license agreement signed label Dec 9, 2025
@etj etj linked an issue Dec 9, 2025 that may be closed by this pull request
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @etj, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly refactors the internationalization (i18n) mechanism for metadata within the GeoNode project. The changes aim to centralize and streamline how localized metadata labels and schemas are managed and accessed. By relocating core i18n components to the 'geonode.base' application, introducing a dedicated 'LabelResolver' for efficient label retrieval, and enhancing the caching strategy, the PR improves modularity, maintainability, and consistency of i18n across the platform. Furthermore, the refactoring includes a cleaner approach to handling database signals related to thesaurus updates, ensuring that i18n caches are invalidated and refreshed appropriately.

Highlights

  • Centralized i18n Logic: The core internationalization mechanism, including caching and label resolution, has been moved from 'geonode/metadata' to 'geonode/base', promoting better modularity and reusability across the application.
  • Enhanced Caching for i18n Data: The 'I18nCache' implementation has been refactored to use a new 'I18nCacheEntry' class and a standard dictionary, replacing 'FIFOCache', for more explicit control over cached language data and improved freshness checks.
  • Introduced LabelResolver: A new 'LabelResolver' class provides a standardized and more robust way to retrieve localized labels, including fallback mechanisms, simplifying i18n text handling throughout the codebase.
  • Decoupled Signal Handling: Signal connections for thesaurus changes are now managed in a dedicated 'geonode/base/signals.py' file and initialized through 'geonode/base/apps.py', separating concerns and improving the application's startup process.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

gemini-code-assist[bot]

This comment was marked as outdated.

@etj etj marked this pull request as ready for review December 9, 2025 00:31
@etj etj marked this pull request as draft December 9, 2025 00:36
@etj
Copy link
Contributor Author

etj commented Dec 9, 2025

/gemini review

@etj etj marked this pull request as ready for review December 9, 2025 09:23
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request refactors the internationalization (i18n) mechanism by moving core logic and signal handling from the metadata application to the base application. This improves modularity and separation of concerns. Key changes include renaming geonode/metadata/i18n.py to geonode/base/i18n.py, introducing a new geonode/base/signals.py for centralized signal connections, and restructuring the caching mechanism with I18nCacheEntry and LabelResolver classes. The changes also involve updating import paths and context keys across various files to reflect the new structure. The introduction of TODO comments is helpful for tracking future improvements.

Comment on lines 79 to +82

def __init__(self):
# the cache has the lang as key, and various info in the dict value:
# - date: the date field of the thesaurus when it was last loaded, it's used for the expiration check
# - labels: the keyword labels from the i18n thesaurus
# - schema: the localized json schema
# FIFO bc we want to renew the data once in a while
self.cache = FIFOCache(16)
# the cache has the lang as key, and I18nCacheEntry as a value:
self.lang_cache = {}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The replacement of FIFOCache with a standard dictionary (self.lang_cache) removes the fixed-size eviction policy. If the number of languages or cached data keys grows large, this could lead to unbounded memory consumption. Consider if an unbounded cache is the desired behavior, or if a size-limited cache (e.g., using functools.lru_cache or a custom implementation) is more appropriate to prevent potential memory issues in a production environment.

Suggested change
def __init__(self):
# the cache has the lang as key, and various info in the dict value:
# - date: the date field of the thesaurus when it was last loaded, it's used for the expiration check
# - labels: the keyword labels from the i18n thesaurus
# - schema: the localized json schema
# FIFO bc we want to renew the data once in a while
self.cache = FIFOCache(16)
# the cache has the lang as key, and I18nCacheEntry as a value:
self.lang_cache = {}
def __init__(self):
# the cache has the lang as key, and I18nCacheEntry as a value:
self.lang_cache = {}

@@ -72,7 +73,7 @@ def update_resource(
):
"""
Called when persisting data, updates the field `field_name` of the resource
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There's a small typo in the docstring. "content content" should be "with the content".

Suggested change
Called when persisting data, updates the field `field_name` of the resource
with the content, where json_instance is the full JSON Schema instance,

@etj etj force-pushed the 13800_i18n_refact branch 5 times, most recently from edcf953 to 31c3aed Compare December 9, 2025 18:03
@codecov
Copy link

codecov bot commented Dec 9, 2025

Codecov Report

❌ Patch coverage is 99.09091% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 74.14%. Comparing base (7c402fd) to head (e37e65b).
⚠️ Report is 8 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #13801      +/-   ##
==========================================
+ Coverage   74.13%   74.14%   +0.01%     
==========================================
  Files         944      944              
  Lines       56291    56321      +30     
  Branches     7617     7623       +6     
==========================================
+ Hits        41730    41761      +31     
+ Misses      12897    12893       -4     
- Partials     1664     1667       +3     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@etj etj force-pushed the 13800_i18n_refact branch from 31c3aed to f2e1406 Compare December 9, 2025 18:53
@etj etj force-pushed the 13800_i18n_refact branch from f2e1406 to e37e65b Compare December 10, 2025 10:34
@etj etj requested a review from mattiagiupponi December 10, 2025 11:17
@etj etj merged commit afca096 into master Dec 10, 2025
17 checks passed
@etj etj deleted the 13800_i18n_refact branch December 10, 2025 18:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed CLA Bot: community license agreement signed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Refact metadata i18n mechanism

2 participants