This repository has been archived by the owner on Jan 9, 2023. It is now read-only.
Translate database strings #549
Labels
needs requirements
indicates that an issue needs more requirements in order to be worked on
wontfix
indicates an issue/pull request will not be worked on
Currently, we have english strings that are displayed to the user stored in the database, this will have to be translated as well.
Most of the strings are
tags
likes status/type/category etc. some of these lists are mutable and others are immutableMutable
- visit-types.js
- inventory-type-list.js
- unit-types.js
- lab-pricing-types.js
immutable
- publish-statuses.js
- payment-profiles.js
- inventory-adjustment-types.js
- imaging-pricing-types.js
- billing-categories.js
Useages:
The translations should be under the
database
namespace, containing a namespace for each mixin. these namespaces will contain all contain keys for each value that should be translated.The solution to usage one is that each mixin should have a computed property called something like
getSelectList
. this will return an array of objects:All usages of the bare type object in select boxes will have to be replaced by this new computed property.
The solution to point 2 could be a handle bars helper
{{translate-database-value value namespace='payments'}}
the helper will search the namespace for a key containing the value. if that key does not exist it will return the value, since it is user created.The text was updated successfully, but these errors were encountered: