[MAGNOLIA-4931] Improve resolving of string properties from ContentMap Created: 28/Mar/13 Updated: 23/Apr/13 Resolved: 23/Apr/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | templating |
| Affects Version/s: | 4.5 |
| Fix Version/s: | 4.5.9, 5.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Zdenek Skodik | Assignee: | Jaroslav Simak |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | performance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Date of First Response: | |||||
| Description |
|
If the string property is single-valued, we automatically apply a link API on it, although this expects an uuid pattern only, so provides unnecessary calls many times (i.e. if subtitle = Home), instead of falling back to returning string value directly. |
| Comments |
| Comment by Jan Haderka [ 23/Apr/13 ] |
|
FYI: this change also lowers number of security checks made per rendering by avoiding property retrieval unnecessarily. |