Django Garnett is a field level translation library that allows you to store strings in multiple languages for fields in Django - with minimal changes to your models and without having to rewrite your code.
Home Page: https://django-garnett.herokuapp.com/
License: BSD 3-Clause "New" or "Revised" License
Alter the json orm lookup so you can do Book.objects.filter(title__en='thing') but not Book.objects.filter(title__notalang='thing')
After getting apps from executor:
executor = MigrationExecutor(connection)
apps = executor.loader.project_state([migration file]).apps
Model = apps.get_model('..', '...')
I Have to pass json into translated field to create object. Otherwise, it will have errors saying 'isn't a valid json token'
Found this via HN and looks like something I could use for a current project.
However, requirements are hard pinned to specific versions, including not-the-latest version of Django.
Could you perhaps be more forgiving and/or specify minimum versions for the required dependencies?
Thanks - especially those of us who have to use Django4. ;-)
When a TranslatedField is not submitted it should be set to a dictionary mapping the current language to the default of the inner character fields. This could be implemented as a partial object that calls some function to do the wrapping, since partial is serializable by the django migration system.
Get rid of TranslatedCharField and TranslatedTextField and use Translated as in the readme but have it be a function that returns a translated X field.
Could have a test for it as well
After changing CharField into Translated(CharField(max_length = 10)), it doesn't return 'allow_blank' and 'null' attributes of the field.
e.g. Translatable( (CharField(...args), fallback=func )
This is so we don't need to create separate translatable fields
A test should also be added to make sure the blank validation is working
Get an error if trying to update or create when using dictionary, eg:
Model.objects.update_or_create(translatable_field={'en': "Some text})
Traceback:
Traceback (most recent call last):
File "/usr/local/bin/django-admin", line 8, in <module>
sys.exit(execute_from_command_line())
File "/usr/local/lib/python3.8/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python3.8/site-packages/django/core/management/__init__.py", line 395, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/lib/python3.8/site-packages/django/core/management/base.py", line 330, in run_from_argv
self.execute(*args, **cmd_options)
File "/usr/local/lib/python3.8/site-packages/django/core/management/base.py", line 371, in execute
output = self.handle(*args, **options)
File "/usr/src/app/python/tablion/tablion/utils/management/commands/load_dataset.py", line 18, in handle
dataset = load_dataset_fixture(passport_type)
File "/usr/src/app/python/tablion/tablion/utils/fixture_loaders.py", line 51, in load_dataset_fixture
dataset, c = models.Dataset.objects.update_or_create(
File "/usr/local/lib/python3.8/site-packages/django/db/models/manager.py", line 85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/django/db/models/query.py", line 589, in update_or_create
obj = self.select_for_update().get(**kwargs)
File "/usr/local/lib/python3.8/site-packages/django/db/models/query.py", line 425, in get
num = len(clone)
File "/usr/local/lib/python3.8/site-packages/django/db/models/query.py", line 269, in __len__
self._fetch_all()
File "/usr/local/lib/python3.8/site-packages/django/db/models/query.py", line 1308, in _fetch_all
self._result_cache = list(self._iterable_class(self))
File "/usr/local/lib/python3.8/site-packages/django/db/models/query.py", line 53, in __iter__
results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size)
File "/usr/local/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1156, in execute_sql
cursor.execute(sql, params)
File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 98, in execute
return super().execute(sql, params)
File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 66, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
return executor(sql, params, many, context)
File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
File "/usr/local/lib/python3.8/site-packages/django/db/utils.py", line 90, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/usr/local/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
django.db.utils.ProgrammingError: can't adapt type 'dict'
Currently the context manager returns the list of selected languages as Language objects, but the available_languages property just returns them as language codes. Would be nice to keep this consistent.
There is also currently no way to get the list of selected languages as language objects from python.
This is the default when using set_cookie, we probably want to make it last longer than this.
Could just use django's session storage so it is tied to the users authentication session. This would also give more control to users of the library as to how it is stored
As suggested in #46
Could maybe just log an error and keep the current language in this case
This should perform a data migration on all translated fields, saving the current text as json in the default language.
e.g. 'Some text' -> '{"en": "Some text"}'
Maybe need to expand test coverage?
Currently it is registered with json.KeyTransform
Make sure we only save dictionary's that are direct string to string mappings e.g. {"lang-code-1": "value", "lang-code-2": "value"}
Right now it is empty https://pypi.org/project/django-garnett/
Should be using this everywhere and should be moving some fields like help_text and verbose_name to the outer field
Based on the order of languages in GARNETT_TRANSLATABLE_LANGUAGES
Will also need a way to get which language is being displayed
Change:
from django.contrib.postgres.fields.jsonb import KeyTextTransform
To
from django.db.models.fields.json import KeyTextTransform
Like the languages setting is
Add some tests for manipulating data through DRF api's
Can publish to pypi on a github release so it is easier to release our changes
Even though we are using black flake8 would be nice to catch unused imports, unused variables etc.
Should have some tests for the logic in get_default_language and get_languages
Mentioned as a future enhancement in the readme
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.