[jira] Closed: (TAPESTRY-1839) Include SymbolSource when looking up component messages

["Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>]

     [ https://issues.apache.org/jira/browse/TAPESTRY-1839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAPESTRY-1839.
------------------------------------------

    Resolution: Won't Fix
      Assignee: Howard M. Lewis Ship

This seems like a good idea, but that's what the global message catalog is for. Perhaps Tapestry needs a per-library message catalog.  In any case, this would significantly change an area of Tapestry: invalid keys would result in exceptions, not the current behavior of highlighting the failure.  SymbolSource is also missing the ability to query for a particular key. Perhaps changing the SymbolSource API could change these.  I do like the idea of being able to use ${...} syntax to compose a message from smaller pieces.

> Include SymbolSource when looking up component messages
> -------------------------------------------------------
>
>                 Key: TAPESTRY-1839
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1839
>             Project: Tapestry
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.0.6
>            Reporter: Dan Adams
>            Assignee: Howard M. Lewis Ship
>
> If symbols were provided in the component messages then we could do things such as setting component defaults that could be overridden by the application. I would like to see SymbolSource included when looking up messages or make the component message sources configurable or both.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org