All specs 1,799 total

scripts/check-ruby.js

Compares two version strings, expecting them as string inputs, and returns an integer indicating their relative order. It parses the dot-separated components of both versions and compares them segment by segment. The function returns 1 if the first version is greater, -1 if the first version is less, and 0 if the versions are identical up to the first three components.

scripts/check-ruby.js

Compares two semantic version strings by splitting them into numeric components and iterating through the parts. It accepts two string arguments representing the versions to be compared. The function returns 1 if the first version is greater than the second, -1 if it is less, and 0 if the versions are identical. This comparison is limited to the first three components of the provided version strings.

scripts/check-ruby.js

Compares two semantic version strings by splitting them into numerical components and iterating through the parts. It accepts two string arguments representing the versions to be compared. The function returns 1 if the first version is greater than the second, -1 if it is less, and 0 if the versions are identical. No external state is modified by this operation.

scripts/check-ruby.js

Compares two semantic version strings, taking them as string inputs. It determines the relative order of the two versions by comparing their numeric components sequentially. The function returns 1 if the first version is greater, -1 if the first version is less, and 0 if the versions are equal. No external state is modified by this operation.

scripts/check-ruby.js

Compares two version strings, expecting them as string inputs, and returns an integer indicating their relative order. It parses the dot-separated components of both versions and compares them sequentially up to the third segment. Returns 1 if the first version is greater, -1 if it is smaller, and 0 if the versions are identical. This function does not modify any external state.

scripts/check-ruby.js

Compares two semantic version strings by splitting them into numeric components and iterating through the parts. It accepts two string arguments representing the versions to be compared. The function returns 1 if the first version is greater than the second, -1 if it is less, and 0 if the versions are equal. No external state is modified by this operation.

scripts/check-ruby.js

Compares two version strings, expecting them as string inputs, and returns an integer indicating their relative order. It parses the dot-separated components of both versions and compares them segment by segment. The function returns 1 if the first version is greater, -1 if the first version is less, and 0 if the versions are identical. No external state is modified by this operation.

scripts/check-ruby.js

Executes a system command to determine the installed Ruby version. It takes no arguments and returns a string representing the major, minor, and patch version number if successful, or null if the command fails or the version string cannot be parsed. The function's primary side-effect is running an external process call to the operating system shell.

scripts/check-ruby.js

Executes a system command to determine the installed Ruby version. It takes no arguments and returns a string representing the major, minor, and patch version number if successful, or null if the command fails or the version string cannot be parsed. This function relies on executing an external process, which is a notable side-effect.

scripts/check-ruby.js

Executes a system command to determine the installed Ruby version. It takes no arguments and returns a string representing the major, minor, and patch version number if successful, or null if the command fails or the version string cannot be parsed. This function relies on executing an external process and has no observable side effects other than reading system information.

scripts/check-ruby.js

Executes a system command to retrieve the installed Ruby version string. It takes no arguments and returns a string representing the major, minor, and patch version number if successful, or null if the command fails or the version pattern is not found. This function relies on executing an external process, which is a notable side-effect.

scripts/check-ruby.js

Executes a system command to determine the installed Ruby version. It takes no arguments and returns a string representing the major, minor, and patch version number if successful, or null if the command fails or the version string cannot be parsed. This function has no observable side-effects other than executing an external process.

scripts/check-ruby.js

Executes a system command to determine the installed Ruby version. It takes no arguments and returns a string containing the major, minor, and patch version numbers if successful, or null if the command fails or the version string cannot be parsed. This function relies on executing an external process, which is its primary side effect.

scripts/check-ruby.js

Executes a system command to determine the installed Ruby version. It takes no arguments and returns a string representing the major, minor, and patch version number if successful, or null if the command fails or the version string cannot be parsed. This function relies on executing an external shell command, which is a notable side-effect.

scripts/check-ruby.js

Executes a system command synchronously to verify its existence and executability. It accepts two string arguments: the command string to test and a descriptive name for error reporting. The function returns a boolean indicating success if the command runs without error, or false if the command fails to execute. A notable side-effect is logging an error message to the console upon failure, suggesting the user install the missing program.

scripts/check-ruby.js

Executes a system command synchronously to verify its existence and executability. It accepts two string arguments: the command string to test and a human-readable name for error reporting. The function returns a boolean indicating success if the command runs without error, or false if the command fails, while also logging an informative error message to the console upon failure.

scripts/check-ruby.js

Executes a system command synchronously to verify its existence and executability. It accepts two string arguments: the command string to test and a descriptive name for error reporting. The function returns a boolean indicating success if the command runs without error, or false if the command fails to execute. A notable side-effect is printing an error message to the console upon command failure.

scripts/check-ruby.js

Executes a system command synchronously to determine its availability. It accepts two string arguments: the command string to test and a descriptive name for error reporting. The function returns a boolean indicating success if the command runs without error, or false if the command fails to execute. A notable side-effect is logging an error message to the console upon command failure.

scripts/check-ruby.js

Executes a system command synchronously to verify its existence and executability. It accepts two string arguments: the command string to test and a human-readable name for error reporting. The function returns a boolean indicating success (true if the command runs) or failure (false if the command fails). A notable side-effect is logging an error message to the console upon command failure.

scripts/check-ruby.js

Executes a system command synchronously to determine its availability. It accepts two string arguments: the command string to test and a descriptive name for error reporting. Returns true if the command executes successfully, and false if the execution fails, while also logging an informative error message to the console upon failure.

scripts/check-ruby.js

Executes a system command synchronously to determine its availability. It accepts two string arguments: the command string to test and a descriptive name for the command. The function returns a boolean indicating success if the command runs without error, or false if the command fails to execute. A notable side-effect is logging an error message to the console upon command failure.

mcp-wrapper.js

Starts an external Ruby process, ensuring necessary prerequisites are met before execution. It takes no inputs and outputs nothing directly, but it manages the lifecycle of the spawned server process. The function registers listeners to handle process termination signals like SIGINT and SIGTERM, ensuring the spawned server is gracefully shut down upon application exit. If any critical error occurs during setup, it logs detailed troubleshooting steps and exits the entire Node.js process.

mcp-wrapper.js

Starts an external Ruby process, inheriting its standard input, output, and error streams for real-time logging. It accepts no explicit inputs but relies on environment setup and a predefined server path. The function outputs nothing directly but manages the process lifecycle, ensuring the main Node.js process exits correctly when the spawned server terminates or when the process receives termination signals like SIGINT or SIGTERM. If any critical setup step fails, it logs detailed error messages and forcefully exits the application.

mcp-wrapper.js

Starts an external Ruby process, ensuring necessary prerequisites are met before execution. It takes no arguments but spawns a child process using the specified server path and working directory, inheriting standard I/O streams. The function manages process lifecycle by trapping termination signals like SIGINT and SIGTERM to gracefully shut down the spawned server, and it exits the main process upon any startup failure.

mcp-wrapper.js

Starts an external Ruby process, inheriting standard input, output, and error streams for real-time interaction. It accepts no explicit inputs but relies on environment variables and a predefined server path. The function outputs nothing directly but manages the lifecycle of the spawned process, ensuring the main Node.js process exits correctly when the server terminates or when signals like SIGINT or SIGTERM are received. If any critical setup step fails, it logs detailed error messages and forcefully exits the application.

mcp-wrapper.js

Starts an external Ruby process, ensuring necessary prerequisites are met before execution. It takes no arguments but manages the lifecycle of the spawned server, inheriting standard input, output, and error streams. The function outputs nothing directly but controls the process exit code upon successful or failed termination of the spawned server. It registers handlers to gracefully shut down both the spawned server and the main process upon receiving interrupt or termination signals.

mcp-wrapper.js

Starts an external Ruby process, ensuring necessary prerequisites are met before execution. It takes no arguments and outputs nothing directly, but it manages the lifecycle of the spawned server process. The function registers handlers to gracefully terminate the server upon receiving system signals like SIGINT or SIGTERM, and it exits the entire Node.js process if the server fails to start or if a fatal error occurs during setup.

mcp-wrapper.js

Starts an external Ruby process, inheriting standard input, output, and error streams for real-time logging. It accepts no explicit inputs but relies on environment setup and a predefined server path. The function outputs nothing directly but manages the lifecycle of the spawned process, ensuring the main Node.js process exits correctly when the server terminates or when termination signals like SIGINT or SIGTERM are received. If any critical setup step fails, it logs detailed error messages and forcefully exits the application.

mcp-wrapper.js

Executes an external command to check the installed version of Ruby. It takes no arguments and returns a Promise that resolves if the Ruby command executes successfully with an exit code of zero. Conversely, the Promise rejects if the Ruby executable cannot be found or if the command exits with a non-zero status code, providing specific error messages in either case.

mcp-wrapper.js

Executes the system command to check the installed Ruby version. It accepts no arguments and returns a Promise that resolves successfully if the command exits with a zero code, or rejects with an error message if the command fails to execute or returns a non-zero exit code. A notable side-effect is that it spawns an external process, which can fail if Ruby is not installed or accessible in the system's PATH.

mcp-wrapper.js

Executes an external command to verify the presence and basic functionality of the Ruby interpreter. It takes no arguments and returns a Promise that resolves successfully if the Ruby command exits with a zero code, or rejects with an error message if the command fails to execute or returns a non-zero exit code. The primary side-effect is spawning a child process to interact with the system's Ruby installation.

mcp-wrapper.js

Executes an external command to check the installed version of Ruby. It takes no arguments and returns a Promise that resolves if the Ruby command executes successfully with an exit code of zero. The Promise rejects if the Ruby executable cannot be found or if the command exits with a non-zero status code, providing specific error messages in those failure cases.

mcp-wrapper.js

Executes the system's ruby interpreter with the --version argument to verify its availability and proper execution. It takes no inputs and returns a Promise that resolves if the command exits successfully with a zero code, or rejects with an error message if the ruby executable cannot be found or if the process fails. The function's notable side-effect is spawning an external operating system process.

mcp-wrapper.js

Executes a system command to check the installed version of Ruby. It takes no arguments and returns a Promise that resolves successfully if the Ruby command exits with a zero code, or rejects with an error message if the command fails to execute or returns a non-zero exit code. A notable side-effect is the spawning of an external process.

mcp-wrapper.js

Executes an external command to check the installed version of Ruby. It takes no arguments and returns a Promise that resolves if the Ruby command executes successfully with an exit code of zero. Conversely, the Promise rejects if the Ruby executable cannot be found or if the command exits with a non-zero status code, providing specific error messages in both failure scenarios.

lib/magi/archive/mcp/tools.rb

Sends a POST request to the /auto_link endpoint using the client object. It accepts a card name, and optional parameters including a linking mode, dry run status, scope, minimum term length, and type inclusion flag. The function constructs a payload from these inputs and transmits it to the specified endpoint. It has no explicit return value but performs an external API call.

lib/magi/archive/mcp/tools.rb

Sends a POST request to the /auto_link endpoint using the client object. It accepts a card name, and optional parameters including a linking mode, dry run status, scope, minimum term length, and type inclusion flag. The function constructs a payload from these inputs and transmits it to the specified endpoint. It has no explicit return value but performs an external network action.

lib/magi/archive/mcp/tools.rb

Sends a POST request to the /auto_link endpoint using the client object. It accepts a card name, and optional parameters including a linking mode, dry run status, scope, minimum term length, and type inclusion flag. The function constructs a payload from these inputs and transmits it to the specified endpoint. It has no explicit return value but performs an external network action.

lib/magi/archive/mcp/tools.rb

Sends a POST request to the /auto_link endpoint using the client object. It accepts a card name, and optional parameters including a linking mode, dry run status, scope, minimum term length, and type inclusion flag. The function constructs a payload from these inputs and transmits it to the specified endpoint. It has no explicit return value but performs an external network action.

lib/magi/archive/mcp/tools.rb

Sends a POST request to the /auto_link endpoint using the client object. It accepts a card name and optional parameters including a linking mode, dry run status, scope, minimum term length, and type inclusion flag. The function constructs a payload from these inputs and transmits it to the specified endpoint. It has no explicit return value but performs an external API call.

lib/magi/archive/mcp/tools.rb

Sends a POST request to the /auto_link endpoint using the client object. It accepts a card name, and optional parameters including a linking mode, dry run status, scope, minimum term length, and type inclusion flag. The function constructs a payload from these inputs and transmits it to the specified API endpoint. It has no explicit return value but performs an external network call.

lib/magi/archive/mcp/tools.rb

Sends a POST request to the /auto_link endpoint using the client object. It accepts a card name, and optional parameters including a linking mode, dry run status, scope, minimum term length, and type inclusion flag. The function constructs a payload from these inputs and transmits it to the specified endpoint. It has no explicit return value but performs an external network action.

lib/magi/archive/mcp/tools.rb

Retrieves a specific AI instruction card by constructing a unique key from the provided section name. It attempts to fetch this card using an external get_card mechanism, returning the card's data structure if it contains non-empty content. If the card is not found or its content is empty, the function returns nothing. This process relies on an external dependency to fetch the card data.

lib/magi/archive/mcp/tools.rb

Retrieves a specific AI instruction card by constructing a unique key from the provided section name. It attempts to fetch this card using an external get_card mechanism, returning the card's data structure if it contains non-empty content. If the card cannot be found or its content is empty, the function returns nil. This process relies on an external dependency, get_card, to perform its primary action.

lib/magi/archive/mcp/tools.rb

Retrieves a specific AI instruction card by constructing a unique key from the provided section name. It attempts to fetch this card using an external mechanism and returns the card's data structure if it contains non-empty content. Otherwise, it returns null. This function relies on an external get_card method and has no observable side effects other than reading data.

lib/magi/archive/mcp/tools.rb

Retrieves a specific AI instruction card by constructing a unique key from the provided section name. It attempts to fetch this card using an external mechanism and returns the card's data structure if it contains non-empty content. Otherwise, it returns null. This function relies on an external get_card method and has no visible side effects other than potentially accessing external resources.

lib/magi/archive/mcp/tools.rb

Retrieves a specific AI instruction card by constructing a unique key from the provided section name. It attempts to fetch this card using an external mechanism and returns the card's data structure if it contains non-empty content. If the card cannot be found or its content is empty, the function returns nothing. This process relies on an external function, get_card, which is not defined here.

lib/magi/archive/mcp/tools.rb

Retrieves a specific AI instruction card by constructing a unique key from the provided section name. It attempts to fetch this card using an external get_card mechanism, returning the card's data structure if it contains non-empty content. If the card cannot be found or its content is empty, the function returns nothing. This process relies on an external dependency, get_card, to perform its core operation.

lib/magi/archive/mcp/tools.rb

Retrieves a specific AI instruction card by constructing a unique key from the provided section name. It attempts to fetch this card using an external get_card mechanism, returning the card's data structure if it contains non-empty content. If the card cannot be found or its content is empty, the function returns nothing. This process relies on an external dependency, get_card, to perform its core operation.

lib/magi/archive/mcp/tools.rb

Retrieves or initializes the content for a weekly summaries table of contents card. It accepts the card name, a date string, and a username as inputs, though only the card name is used internally for fetching. If the designated table of contents card is not found, it initializes the content as an empty HTML ordered list. The function returns the content string of the table of contents card, or an empty list structure if it had to be created.