Closed patel-malav closed 5 months ago
In the current implementation on lables like apply, cancel, search, reset, next and prev are getting translated.
table headers should also be translated provided that there is a translation available. The same goes for the search form input labels.
The static fetchTranslations should handle this responsibility of collecting all the keys that needs translation.
These keys already exists in markup in data-search-with and classhelper a data-helpurl=".....&properties="..."&......"
So collect these keys make an API request and populate the static translations object
@rouilj PR - https://github.com/UMB-CS-682-Team-03/tracker/pull/64
have changes for this
Merged PR - #64 Marking this as completed
In the current implementation on lables like apply, cancel, search, reset, next and prev are getting translated.
table headers should also be translated provided that there is a translation available. The same goes for the search form input labels.
The static fetchTranslations should handle this responsibility of collecting all the keys that needs translation.
These keys already exists in markup in data-search-with and classhelper a data-helpurl=".....&properties="..."&......"
So collect these keys make an API request and populate the static translations object