Static Site Editor can’t be opened in projects belonging to a subgroup
What does this MR do?
It fixes a bug that does not allow to open the Static Site Editor in a project located within a subgroup, for example: gitlab-com/subgroup/project-name.
How to reproduce it?
Open this URL: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/sse/master%2FREADME.md. It uses the Static Site Editor to edit the README.md file of a project within a subgroup. The Static Site Editor does not initialize.
Problem
namespace returns only parent namespace of the project without taking into consideration that it can belong to a group.
Solution
Return full path of the namespace with groups and subgroups.
Screenshots
Project that belongs to a subgroup
Without fix
With the fix
Markdown file opened in Static Site Editor mode
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team