metadata¶
Description¶
Commands for generating and managing package metadata.
Available Commands:
generate: Generate metadata JSON files for packages
validate: Validate existing metadata files
Subcommands¶
generate¶
Generate metadata JSON files for packages.
Required Parameters:
root: Path to root directory containing packages.json. Default: current directory
target_name: Name of the package to generate metadata for (e.g., contract/author/name/version)
target_id: Identifier for the metadata file (used in output filename)
Optional Parameters:
strict (--strict): Enable strict validation of metadata. (Default: False)
all (--all): Generate metadata for all packages. (Default: False)
Usage: Generate for specific package: adev metadata generate . contract/author/package/0.1.0 01
Generate for all packages:
adev metadata generate . contract/author/package/0.1.0 01 --all
Generate with strict validation:
adev metadata generate . contract/author/package/0.1.0 01 --strict
Notes¶
- Reads package information from packages.json
- Generates metadata files in mints/
.json - Strict mode enforces additional validation
- Can process single package or all packages
validate¶
Validate metadata files for packages.
Required Parameters:
metadata_file: Path to the metadata JSON file to validate
Usage: Validate a metadata file: adev metadata validate mints/01.json
Notes¶
- Validates the metadata file format and content
- Checks if all dependencies are minted
- Verifies component status in mapping.txt
- Displays detailed validation results with verbose flag
- Exits with error if validation fails