Comming v1.5.0

[albertalef]

Added

• Parallel Execution (#34)

  sh do
    results = parallel do
      curl("https://api1.example.com")
      curl("https://api2.example.com")
      chain { ls | wc("-l") }
    end
  
    results.each { |r| puts r }
  end

  • Returns an Enumerator with results in completion order
  • Supports regular commands, chains, and sh() calls
  • Errors are captured and returned as values (not raised)

• Chain Options (#34)

  # Debug mode for chains
  chain(debug: true) { ls | grep("test") }
  
  # Parse chain output
  chain(parse: :json) { curl("https://api.example.com") }

• Environment Variables (#47)

  # Command-level
  sh.npm("start", _env: { NODE_ENV: "production" })
  
  # Block-level
  sh(env: { DATABASE_URL: "postgres://localhost/db" }) do
    rake("db:migrate")
  end
  
  # Global
  RubyShell.env[:API_KEY] = "secret"
  RubyShell.config(env: { DEBUG: "true" })

• Debug Mode (#39)

  # Global
  RubyShell.debug = true
  
  # Block scope
  RubyShell.debug { sh.ls }
  
  # Per command
  sh.git("status", _debug: true)

• Output Parsers (#38)

  sh.cat("data.json", _parse: :json)   # => Hash
  sh.cat("config.yml", _parse: :yaml)  # => Hash
  sh.cat("users.csv", _parse: :csv)    # => Array

Changed

• BREAKING: Renamed _env to env in RubyShell.config and sh block options (#34)

  # Before
  RubyShell.config(_env: { DEBUG: "true" })
  sh(_env: { NODE_ENV: "production" }) { ... }
  
  # After
  RubyShell.config(env: { DEBUG: "true" })
  sh(env: { NODE_ENV: "production" }) { ... }

  Note: Command-level _env option remains unchanged.

• Refactored specs directory structure

[albertalef]

About the _env breaking change, is to make more obvious the usage of settings. Like:

If we are adding settings on a command, we use the prefix "_".

But if we are adding settings on a clause (sh, chain, parallel), we dont need to add the "_" prefix