[
https://issues.jboss.org/browse/TEIIDDES-1857?page=com.atlassian.jira.plu...
]
Rob Stryker commented on TEIIDDES-1857:
---------------------------------------
The new impl looks good to me. But I do have 1 other complaint. It'd be best if the
error message could indicate which filesystem there might be an error on. For example,
when iterating through the list of windows reserved words, the error message should
indicate that. If it's a reserved word in Mac, then the error message should indicate
that.
I could also see a use-case where you might wish to pass in a list of OS's you want to
validate against. For example if you know your usecase does NOT include Mac, you may want
to pass in BYTE_WIN | BYTE_LINUX, or if you want to validate against all, BYTE_ALL =
BYTE_WIN | BYTE_MAC | BYTE_LINUX.
This last section is just a suggestion, but I think the error messages do need to be fixed
to be more clear.
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.4
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