Skip to content
Nappai Documentation

Code Linter

The Code Linter component checks your source code for syntax errors in many programming languages. It helps you catch mistakes before you run or deploy your code.

How it Works

The component uses Tree‑sitter, a fast parsing library, to analyze the structure of your code. When you provide a snippet of code and select a programming language, the component runs the corresponding Tree‑sitter parser locally on your machine. It then reports any syntax errors it finds. Because everything happens locally, there are no external API calls and no data leaves your environment.

Inputs

Mapping Mode

This component has a special mode called “Mapping Mode”. When you enable this mode using the toggle switch, an additional input called “Mapping Data” is activated, and each input field offers you three different ways to provide data:

  • Fixed: You type the value directly into the field.
  • Mapped: You connect the output of another component to use its result as the value.
  • Javascript: You write Javascript code to dynamically calculate the value.

This flexibility allows you to create more dynamic and connected workflows.

Input Fields

  • Programming Language: Choose the language of the code you want to validate. Supported languages are php, javascript, python, typescript, csharp, go, java, c, cpp, swift, kotlin.

  • Mapping Mode: Toggle this switch to enable mapping mode, which lets you process multiple data records in batch.

  • Source Code: Paste or provide the source code that you want to check for syntax errors.

  • Tool Name: When this component is used as a tool for an agent, this is the name that will appear in the agent’s tool list.

  • Tool Description: A detailed description of what this tool does, helping the agent decide when to use it.

  • Tools arguments metadata: Defines the metadata for the arguments that the tool will accept.

Outputs

  • Lint Result: A data object that contains the results of the linting process, including any syntax errors found and their locations.

  • Tool: A tool object that can be passed to an agent, allowing the agent to call the linter as part of its decision‑making process.

Usage Example

  1. Drag the Code Linter component onto your workflow canvas.
  2. Set Programming Language to python.
  3. Paste a Python script into Source Code.
  4. (Optional) Enable Mapping Mode if you want to validate many scripts at once.
  5. Run the workflow.
  6. The Lint Result output will show any syntax errors, and the Tool output can be used by an AI agent to decide whether the code is ready to run.
  • Code Formatter – Automatically formats code to a consistent style.
  • Static Analyzer – Performs deeper code analysis for potential bugs and security issues.
  • Code Quality Checker – Evaluates code against quality metrics and best practices.

Tips and Best Practices

  • Use Mapping Mode when you need to validate a batch of files or code snippets.
  • Always select the correct Programming Language; the parser will only work for the language you choose.
  • If you’re integrating the linter into an AI agent, provide a clear Tool Description so the agent understands when to use it.
  • Keep the Source Code input concise; large files may increase processing time.

Security Considerations

The linter runs entirely on your local machine and does not send any code to external services. This ensures that your source code remains confidential and that no sensitive data is exposed.