Api will regard numberlic namespace path as a namespace id.
Summary
Api will regard numberlic namespace path(like 12345678) as a namespace id.
Can't fork projects to a "numberlic" namespace via API.
Steps to reproduce
Create a user with a "numeberlic" username (like 12345678), and fork a project to its own namespace using API. A 404 Target Namespace Not Found will be returned.
Also, a group with a numberlic name will do.
Example Project
curl --header "Private-Token: <My Token>" https://gitlab.com/api/v4/projects/leoleoasd%2Ftest/fork -X POST -d "namespace=12312413123123"will response {"message":"404 Target Namespace Not Found"}.
12312413123123 is a group I created.
What is the current bug behavior?
Response {"message":"404 Target Namespace Not Found"}.
What is the expected correct behavior?
Fork to that namespace.
I only tested fork project API, but I think this bug may happen on any API that requires a "namespace id or path".