GitLab Code Splitter

Split GitLab repository code into manageable chunks

System → Get Languages

AI-generated

Overview

This node, named "GitLab Code Splitter," interacts with an external API to process GitLab repository code and system information. Specifically for the System - Get Languages operation, it retrieves a list of supported programming languages from the API.

Common scenarios where this node is beneficial include:

  • Discovering which programming languages are supported by the code splitting service before processing code.
  • Integrating with GitLab repositories to split large codebases into manageable chunks for analysis or further processing.
  • Performing health checks on the API service (other system operations).

Practical example:

  • Before splitting code files in a GitLab repository, you can use the "Get Languages" operation to fetch all supported languages, then dynamically configure subsequent steps based on available language support.

Properties

Name Meaning
Split Options Collection of options controlling how code is split into chunks:
- Max Tokens: Maximum tokens per chunk (default 800)
- Overlap: Token overlap between chunks (default 50)
- Min Chunk Size: Minimum chunk size in tokens (default 100)
- Preserve Newlines: Whether to preserve newline characters (default true)

Note: For the System - Get Languages operation, only the "Split Options" property is defined as input, but it is not used in this operation.

Output

The output JSON structure for the Get Languages operation is the direct response from the API endpoint /api/languages. It typically contains a list or array of supported programming languages, each likely represented by language names or identifiers.

Example output (conceptual):

[
  "go",
  "javascript",
  "python",
  "java",
  ...
]

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external GitLab Code Splitter API.
  • The API URL and API key must be configured in the node credentials.
  • The node makes HTTP GET requests to the API endpoint ${apiUrl}/api/languages with the API key included in headers.
  • No other external services or environment variables are required specifically for this operation.

Troubleshooting

  • Invalid API URL provided in credentials: Ensure the API URL is a valid URL format.
  • Valid API key is required and must be provided in credentials: The API key must be 10-200 characters long, contain only alphanumeric characters, hyphens, and underscores, and must not be a placeholder or common invalid value.
  • Invalid API key format: The node validates the API key format before making requests; ensure your key meets the criteria.
  • Network errors or timeouts: Check network connectivity to the API URL and that the API service is operational.
  • API returns error responses: Verify that the API key has sufficient permissions and that the API service supports the requested operation.

Links and References


This summary is based solely on static analysis of the provided source code and input properties.

Discussion