paul chipchase 39f6471fad Fix the perforce source control api returning invalid file paths when the users client spec root ends with a '/'or '\' ...

#rb Brooke.Hubert, Patrick.Laflamme
#rnx
#preflight 63d7927df62671520156e69d

- CL 23859876 introduced optimizations that consider a filepath to be invalid if the path contains consecutive path separators (DirA//DirB for example instead of DirA/DirB) and although no issues were seen when testing we fairly quickly ran into a user facing errors when trying to submit work from the editor.
- The users client spec root had a '\' at the end of it where as most internal devs do not. This in turn caused problems when parsing file info from source control as the code was assuming that the client spec root had no trailing separator and was adding one.
- We now normalize the client spec root after we parse it via a call to FPaths::NormalizeDirectoryName which should enforce that the root path match all our usual expectations.

[CL 23945309 by paul chipchase in ue5-main branch]

2023-02-01 04:04:01 -05:00

..

PerforceSourceControl

Fix the perforce source control api returning invalid file paths when the users client spec root ends with a '/'or '\'

2023-02-01 04:04:01 -05:00