[MAGNOLIA-3925] MagnoliaTemplatingUtilities.createLink should have a version where you can supply a custom extension... or none at all Created: 22/Dec/11 Updated: 05/Jan/16 Resolved: 05/Jan/16 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | templating |
| Affects Version/s: | 4.4.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Will Scheidegger | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
mgnl.createLink() seems to be the proper way to add links to your template. Unfortunately when you need a link with a selector (e.g. /link/to/my/page.with.3.selectors.html), you're out of luck since createLink() always appends ".html" to the link. You would have to remove the extension, add the selectors and append the extension back to the link (= ugly hack). It would be better to have createLink methods where you can also provide the extension, or if set to null or "" no extension is added at all. |
| Comments |
| Comment by Michael Mühlebach [ 05/Jan/16 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |