Add webPath field to NamespaceType GraphQL type

What does this MR do and why?

Adds the webPath field to the Namespace GraphQL type, exposing the namespace path relative to the instance root.

This allows frontend consumers to retrieve the namespace path directly via GraphQL without constructing it manually from other fields. The field supports the :api, :read_api, and :ai_workflows token scopes, consistent with other path/URL fields on the type.

Files changed:

  • app/graphql/types/namespace_type.rb — adds the web_path field and resolver method
  • spec/graphql/types/namespace_type_spec.rb — adds field to expected fields list, verifies :ai_workflows scope, and adds a unit test for the resolver
  • doc/api/graphql/reference/_index.md — documents the new field in the GraphQL reference
  • public/-/graphql/introspection_result.json — updated introspection snapshot
  • public/-/graphql/introspection_result_no_deprecated.json — updated introspection snapshot (no deprecated fields)

References

Screenshots or screen recordings

Before After
N/A (GraphQL type change) N/A (GraphQL type change)

How to set up and validate locally

  1. Start a local GDK instance.
  2. Navigate to the GraphQL explorer at http://localhost:3000/-/graphql-explorer.
  3. Run the following query:
    query {
      namespace(fullPath: "your-group-or-project") {
        webPath
        webUrl
      }
    }
  4. Verify webPath returns the path relative to the instance root (e.g., /groups/my-group).

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports

Loading
Loading