Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Catalog namespaces

See original GitHub issue

I’ve been thinking about namespaces for a while and made me to write it down.

Multiple namespaces

Sometimes are messages split in several message catalogs. Both catalogs might contain message with the same ID and it that case it would be overwritten without namespacing messages from different catalogs.

This feature already exists in most i18n libs.

Local namespaces

What’s more interesting and what I actually would like to do are local namespaces. There’re two possible use cases:

  1. Reusable components
  2. Code splitting

Reusable components

Imagine you have a React component and you want to ship translations with it. Ideally, developer using this component should just spin up it’s own i18n provider to activate language, but the messages should be loaded directly from component. All translations inside this components should be tied to the component only.

lingui-cli should only extract messages from 3rd party components if it isn’t translated in some language, otherwise it should ignore it

Code spliting

As we split the code, we should be able to split the message catalog. This should be fully automated: only messages in bundled code are added to the bundle.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:11
  • Comments:8 (3 by maintainers)

github_iconTop GitHub Comments

vsnigcommented, Mar 7, 2018

Catalog splitting is an absolutely necessary feature for any real world website or SPA. Is it planned to implement anytime soon?

tricoder42commented, Aug 8, 2018

@saravanan10393 end of August sounds reasonable, definitely mid September.

Read more comments on GitHub >

github_iconTop Results From Across the Web

SupportsNamespaces (Spark 3.2.1 JavaDoc)
Catalog methods for working with namespaces. If an object such as a table, view, or function exists, its parent namespaces must also exist...
Read more >
Documentation: 15: 53.32. pg_namespace - PostgreSQL
The catalog pg_namespace stores namespaces. A namespace is the structure underlying SQL schemas: each namespace can have a separate collection of relations, ...
Read more >
ArcGIS.Desktop.Catalog Namespace
This namespace contains classes that represent different types of project items such as folder connections, database connections, server connections, ...
Read more >
Definitive Guide to Namespace Analysis - GitLab
This page defines the Namespace along with the relationship to Workflow groups as well ... Data Team · Data Catalog; Definitive Guide to...
Read more >
Microsoft.Spark.Sql.Catalog Namespace - .NET for Apache ...
Explore all classes and interfaces of the Microsoft.Spark.Sql.Catalog namespace.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found