For all of these modules, we've turned off CoffeeScript's normal outer function
wrapper, as each module is just a call to define() with a function that fulfills
the same purpose. This one is different, as it is necessary to compute one of the dependencies.
On the server t5/core/messages/<locale> is actually generated dynamically, as is a simple
mapping of message keys to message values, from the global application message catalog.
This module provides access to localized messages from the Tapestry applications' server-side
application message catalog (which is, itself, built from multiple resources, some provided by
the framework, others provided by the application, or third-party libraries).
Messages in the catalog that contain Java-style format specifiers are not included, as there
is no facility for formatting those on the client. This is actually done as a simple test for the
presence of the % character. In addition, any message key that begins with "private-" is
assumed to contain sensitive data (such as database URLs or passwords) and will not be
exposed to the client.
t5/core/messages
For all of these modules, we've turned off CoffeeScript's normal outer function wrapper, as each module is just a call to
define()with a function that fulfills the same purpose. This one is different, as it is necessary to compute one of the dependencies. On the servert5/core/messages/<locale>is actually generated dynamically, as is a simple mapping of message keys to message values, from the global application message catalog.This module provides access to localized messages from the Tapestry applications' server-side application message catalog (which is, itself, built from multiple resources, some provided by the framework, others provided by the application, or third-party libraries).
Messages in the catalog that contain Java-style format specifiers are not included, as there is no facility for formatting those on the client. This is actually done as a simple test for the presence of the
%character. In addition, any message key that begins with "private-" is assumed to contain sensitive data (such as database URLs or passwords) and will not be exposed to the client.