ImportLocalizedLists is placed on FLExProject directly - violates domain-namespace convention

[MattGyverLee]

Found during /lex-lead deep review of commit 969fe09.

Problem

Every other catalog/import in this codebase is namespaced behind a domain operations property:

• project.SemanticDomains.ImportCatalog()
• project.Anthropology.ImportCatalog()
• project.Phonemes.ImportCatalog()

The new methods (ImportLocalizedLists, ImportLocalizedListsForEnabledWS) hang directly off FLExProject as peers of OpenProject / CloseProject -- breaking that convention.

Localized lists do span multiple domains (SemDom + AnthroList + LexDb), but a project.LocalizedLists (or project.Lists) operations property would preserve the discovery model and keep the API user-centric (CLAUDE.md "User-Centric Not Technology-Centric").

Why it matters

• Users won't find these methods via tab-completion under project.SemanticDomains. where they conceptually belong
• Adds two top-level methods to FLExProject instead of one accessor, growing the discovery surface
• The convention is well-established; deviating without strong reason cements the inconsistency
• progress=None parameter pattern is established on *Operations.ImportCatalog but not on FLExProject itself — namespacing also fixes that (mentioned below)

Proposed correction

Introduce a new LocalizedListsOperations (or ListsOperations) class that owns these methods:

project.LocalizedLists.Import(language_code)
project.LocalizedLists.ImportForAllAnalysisWritingSystems()  # better name, see naming issue

FLExProject exposes them via a lazy @property LocalizedLists accessor that returns the operations instance, mirroring how SemanticDomains is wired.

Found by

lex-author P0 review of 969fe09

Related

• See the naming issue (ImportLocalizedListsForEnabledWS is encoded-style) -- both fixes ride together

[MattGyverLee]

Code Analysis — namespace recommendation

File: flexlibs2/code/FLExProject.py

Every other catalog/import is namespaced: project.SemanticDomains.ImportCatalog(), project.Anthropology.ImportCatalog(), project.Phonemes.ImportCatalog(). ImportLocalizedLists and ImportLocalizedListsForEnabledWS sit directly on FLExProject as peers of OpenProject/CloseProject, breaking the discovery model.

Recommendation: Create flexlibs2/code/Lists/LocalizedListsOperations.py and expose via a lazy @property on FLExProject:

@property
def LocalizedLists(self):
    if "_localized_lists_ops" not in self.__dict__:
        from .Lists.LocalizedListsOperations import LocalizedListsOperations
        self._localized_lists_ops = LocalizedListsOperations(self)
    return self._localized_lists_ops

Access becomes:

• project.LocalizedLists.Import("fr") ← was project.ImportLocalizedLists("fr")
• project.LocalizedLists.ImportForEnabledWS() ← was project.ImportLocalizedListsForEnabledWS()

LocalizedLists is unambiguous despite spanning multiple domains (SemDom + AnthroList + LexDb), because the operation is about translated list data, not about managing the lists themselves. Keep the old names as deprecated aliases on FLExProject for one release cycle to avoid a hard break.

Note: This refactor is the right place to also fix the deferred import issues from #77 (move os, FLExGlobals, FP_FileNotFoundError to module-top imports in the new class).

---

Generated by Claude Code