[
https://issues.apache.org/jira/browse/TAP5-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847765#action_12847765
]
Christian Riedel commented on TAP5-1007:
----------------------------------------
Why not make everything case insensitive? I couldn't imagine why someone should
write two different components with the same name like "MyComponent.java" and
"Mycomponent.java". I mean, using components in templates works if you specify
<t:myCOMpoNENT /> and <t:MyComponent />, so Tapestry makes no difference
anyway.
I would rather throw an error when two components with the same (toLowerCase)
name are existent and ignore the case when looking template files. (more user
friendly IMHO)
> When Tapestry is loading templates or other files on case-insensitive OSs
> (Windows) it should trigger an error if the file name case is incorrect
> (which will result in a runtime failure on case-sensitive OSs, such as Linux)
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1007
> URL: https://issues.apache.org/jira/browse/TAP5-1007
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-component-report
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
>
> In other words, on Windows you might find file "myComponent.tml" when it
> should be named "MyComponent.tml" (to match the name of the class,
> MyComponent). This is irritating to find in testing or production, and
> Tapestry should be able to add a check that the case of the file name does
> not match the expected case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
