-
Bug
-
Resolution: Done
-
Critical
-
6.0.0
Description of problem:
There used to be file name validation. It doesn't work now. I was able to create an asset (project, enumeration) with name:
,./<>?:"|;'[]{}=-_+()~`!@#$%^&*
Also, it is possible to use the following as group id, artifact id and version in the new project popup:
,./?:"|;'[]{}=-_+()~`!@#$%^*
That popup checks only for <, > and &.
Causes whole bunch of problems. For example, naming a drl file something/ results in a folder called something being created and a metafile editor being opened for .drl file.
Version-Release number of selected component (if applicable):
BR/PMS 6.0 ER2
- blocks
-
RHBPMS-635 Tracking bz for user experience session
- Closed
- is blocked by
-
RHBRMS-321 New Project dialog allows whitespaces, business-central cannot handle them
- Closed
- is related to
-
RHBRMS-321 New Project dialog allows whitespaces, business-central cannot handle them
- Closed
-
RHBRMS-662 Copy, Rename: File name validation broken
- Closed
-
RHBRMS-991 Broken renaming when there is a dot in the file name
- Closed
-
RHBRMS-1843 Create new project duplicate pop-up
- Closed
-
RHBRMS-245 Plus sign in a file name causes error pop-up
- Closed
-
RHBRMS-1187 Create new Package dialog displays no warning when using " in package name
- Closed
- relates to
-
RHBRMS-321 New Project dialog allows whitespaces, business-central cannot handle them
- Closed
-
RHBRMS-662 Copy, Rename: File name validation broken
- Closed
-
RHBRMS-991 Broken renaming when there is a dot in the file name
- Closed
-
RHBRMS-1843 Create new project duplicate pop-up
- Closed
-
RHBRMS-245 Plus sign in a file name causes error pop-up
- Closed
-
RHBRMS-1187 Create new Package dialog displays no warning when using " in package name
- Closed