genfile 0.6.0

CLI for genfile_core template archive management - create, manage, and materialize code generation templates.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57

//! genfile CLI - Template archive management
//!
//! Command-line interface for `genfile_core` library providing template archive
//! creation, management, and materialization capabilities.

use unilang::pipeline::Pipeline;
use unilang::interpreter::ExecutionContext;

mod commands;
mod handlers;
mod error;
mod repl;

fn main() -> Result< (), Box< dyn core::error::Error > >
{
  let argv : Vec< String > = std::env::args().collect();

  // Create command registry — CommandDefinition structs registered in commands module
  let registry = commands::create_registry()?;

  // Create pipeline for command processing
  let pipeline = Pipeline::new( registry );

  // If no arguments provided, start REPL mode
  if argv.len() == 1
  {
    return repl::run_repl( &pipeline );
  }

  // Otherwise, process single command in CLI mode
  let ctx = ExecutionContext::default();
  // Workaround(issue-001): ExecutionContext has no state field; handlers use thread-local state.
  // Root cause: unilang::ExecutionContext is a plain default-constructible marker; no user data slot.
  // Pitfall: If unilang adds context state later, update all handler registrations to pass state.

  let result = pipeline.process_command_from_argv( &argv[ 1.. ], ctx );

  if !result.success
  {
    eprintln!( "{}", result.error.unwrap_or_default() );
    // Workaround(issue-004): All errors exit with code 1; error category not exposed by unilang.
    // Root cause: unilang::ErrorData has no error-category field; can't distinguish user vs system errors.
    // Pitfall: When unilang exposes error category, map to: user-input=2, system=3, internal=4.
    std::process::exit( 1 );
  }

  // Print command outputs
  for output in result.outputs
  {
    if !output.content.is_empty()
    {
      println!( "{}", output.content );
    }
  }

  Ok( () )
}