Until now the plugin did only allow to localize contents from a json file that followed a certain naming guidelines. With the proposed changes, the localize method can now receive an object as a parameter, instead of the name of a language pack.
This feature might be useful if you'll be retrieving your texts from an external service whose url doesn't match the "{pathPrefix}/{filename}-{lang}.{extension}" syntax.
The new code will only be applied when the received parameter is an object: otherwise, the plugin will expect the parameter to be a language pack name and keep its default behavior. The README.md file has been updated explaining the new feature, and I've also included a new subdirectory in the examples folder to illustrate how it works.
Until now the plugin did only allow to localize contents from a json file that followed a certain naming guidelines. With the proposed changes, the
localizemethod can now receive an object as a parameter, instead of the name of a language pack.This feature might be useful if you'll be retrieving your texts from an external service whose url doesn't match the
"{pathPrefix}/{filename}-{lang}.{extension}"syntax.The new code will only be applied when the received parameter is an object: otherwise, the plugin will expect the parameter to be a language pack name and keep its default behavior. The
README.mdfile has been updated explaining the new feature, and I've also included a new subdirectory in the examples folder to illustrate how it works.This set of changes should solve issue #62.