Skip to content

Structuration of JSON could be improved #17

@Acetoshi

Description

@Acetoshi
Image

I’d like to suggest switching to a field-based localization structure instead:

"name": {
  "en": "...",
  "fr": "...",
  "es": "..."
},
"category": {
  "en": "...",
  "fr": "...",
  "es": "..."
},
"subcategory": {
  "en": "...",
  "fr": "...",
  "es": "..."
}

Advantages

  • Easier access to a single field across all languages
  • Simplifies partial translations and fallback handling
  • Reduces duplication of object structures
  • Makes field-level validation and typing clearer
  • Improves maintainability when adding new translatable fields
  • More convenient for frontend forms and translation tooling

This structure may also make the schema more scalable as the number of translatable fields grows.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions