[
https://issues.jboss.org/browse/TEIIDDES-1857?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on TEIIDDES-1857:
-----------------------------------------------
I like the idea of a general validator but we should be careful to not make this too
complicated for something that is after all a corner case.
i.e. don't add ui component that validates with tons of checkboxes for each os type
since the os type is just one part of this; also mixed case files can be a concern
depending if the file system allows it or not (which is not dependent on the OS).
Better would in my mind be that users gets *warned* about common issues for other OS's
than the one running: i.e. using special characters like # is possible on osx/mac but is
okey on linux.
Then just have the UI state something like "Warning: Sh$T #p.vmd is possible on this
OS, but is not a portable file name on <OS that has issues> because # is not
allowed."
Create and implement a cross-platform file name validator
---------------------------------------------------------
Key: TEIIDDES-1857
URL:
https://issues.jboss.org/browse/TEIIDDES-1857
Project: Teiid Designer
Issue Type: Enhancement
Components: Validation
Affects Versions: 8.2
Reporter: Barry LaFond
Assignee: Paul Richardson
Fix For: 8.2.x-prod-eds6.0
Currently, Teiid Designer allows creating models with pretty much and character in it
besides ".".
Unfortunatelly, a LOT of special characters are not valid on some OS's like Windows,
so opening a project containing invalid Windows file names in Eclipse will probably cause
issues.
Need to create a utility class/framework that can perform name validation across
OS's.
Teiid has reserved model names: _TEMP_, SYS, or SYSADMIN
For Windows chars and reserved words:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.8...
For more comprehensive list and links:
http://en.wikipedia.org/wiki/Filename
Other potential features:
* setNoSpaces(boolean)
* ignoredSystems(WINDOWS, OSX) (i.e. turn off one or more OS types)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira