json_parser_linter 1.0.4

Analysis server plugin to enforce json_coder compatible structures.

json_parser_linter

Analysis server plugin to enforce json_coder compatible structures.

Note: This package is a part of the json_coder suite.

🚀 Getting started

1. Add json_parser_annotations dependency

From pub.dev

dependencies:
  json_parser_annotations: ^1.0.1

From Git repo

dependencies:
  json_parser_annotations:
    git:
      url: https://github.com/Ragibn5/dart-flutter-packages.git
      path: json_coder/json_parser_annotations
      ref: json_coder/json_parser_annotations-1.0.1

The json_parser_annotations package provides the following annotations used to trigger this plugin's linting rules:

Annotation	Purpose
@GenerateJsonParser	When used with json_parser_generator, registers the annotated class in the generated JSON parser registry. When used with this plugin, also enables linting analysis to report incompatible state and structures.

2. Register the plugin in analysis_options.yaml

From pub.dev

plugins:
  json_parser_linter:
    version: ^1.0.4
    diagnostics:
      json_parser_requirements: true

From Git repo

plugins:
  json_parser_linter:
    git:
      url: https://github.com/Ragibn5/dart-flutter-packages.git
      path: json_coder/json_parser_linter
      ref: json_coder/json_parser_linter-1.0.4
    diagnostics:
      json_parser_requirements: true

Should be added as a top level block, i.e., at the same level as include.

3. (Optional) Create a json_parser_linter_config.yaml

Place the file at the root of your project to customize logging and scan scope. The file is entirely optional — if omitted, the plugin uses these defaults:

Setting	Default
Logging	Disabled
Scanned directories	lib/ only

Below is a sample config with all available options. Every field is optional — omitted values fall back to the defaults above.

# ==========================================
# Configuration for `json_parser_linter` plugin
# ==========================================

# Global log configuration: controls diagnostic logging for all rules.
log_config:
  enabled: true        # Enable or disable logging (default: false)
  allow_info: false    # Allow info-level messages (default: false)
  allow_warning: true  # Allow warning-level messages (default: true)
  allow_error: true    # Allow error-level messages (default: true)
  # Relative path (from project root) where log files are saved.
  # default: logs/analyzer_plugins/json_parser_linter
  log_dir_relative_path: logs/analyzer_plugins/json_parser_linter

# Global scan configuration: controls which directories are scanned.
scan_config:
  scan_lib_dir: true   # Scan the lib/ directory (default: true)
  scan_test_dir: false # Scan the test/ directory (default: false)

4. Annotate your classes

Add the @GenerateJsonParser annotation to any class you want the linter to check:

import 'package:json_parser_annotations/json_parser_annotations.dart';

@GenerateJsonParser()
class User {
  final int id;
  final String name;

  User({required this.id, required this.name});

  Map<String, dynamic> toJson() => {'id': id, 'name': name};

  factory User.fromJson(Map<String, dynamic> json) {
    return User(id: json['id'] as int, name: json['name'] as String);
  }
}

Only annotated classes are checked. Abstract classes and non-class declarations are ignored.

5. Verify

Run flutter pub get, then run flutter analyze to verify the plugin is enabled and reporting diagnostics. You may also want to restart the analysis server after each change to the analyzer config (including initial setup).

🔍 Rules

The rule applies only to concrete classes annotated with @GenerateJsonParser. Abstract classes and non-class declarations are ignored.

json_parser_requirements

Reports missing or invalid toJson / fromJson members required for JSON parser generation.

Check	Reported?	Why
Missing toJson instance method	Yes	Required for serialization
toJson is a getter, takes params, or has a wrong return type	Yes	Signature must match generator contract
Missing both factory and static fromJson	Yes	Required for deserialization
fromJson has wrong params or return type	Yes	Signature must match generator contract
Valid toJson + factory or static fromJson	No	Meets requirements
Abstract class / non-class annotation target	No	Not applicable

Required shapes:

• Instance method: Map<String, dynamic> toJson() (or Map<String, Object?>)
• Factory: factory YourClass.fromJson(Map<String, dynamic> json) (or Map<String, Object?>), or
• Static method: static YourClass fromJson(Map<String, dynamic> json) (or Map<String, Object?>)

🐛 Debugging

To see diagnostic logs from the plugin, enable logging in json_parser_linter_config.yaml:

log_config:
  enabled: true

Log files are written to the path specified by log_dir_relative_path (defaults to logs/analyzer_plugins/json_parser_linter/ relative to your project root). Each run creates a daily log file named LOG-dd-MM-yyyy.log.

You can control which severity levels are logged. By default, info is disabled as it is very verbose. To enable all levels:

log_config:
  enabled: true
  allow_info: true     # Disabled by default — very verbose
  allow_warning: true  # Enabled by default
  allow_error: true    # Enabled by default

If you are not seeing expected diagnostics, try:

• Restarting the analysis server (flutter analyze or restart the IDE's Dart analysis server).
• Ensuring the class is annotated with @GenerateJsonParser and is not abstract.
• Ensuring scan_test_dir: true if the file is under test/.
• Checking your json_parser_linter_config.yaml for invalid YAML syntax or incorrect indentation. If the file is malformed, the plugin may crash or fall back to default silently.

📄 Example

See the app_template project for a complete demonstration.