Crystal good first issues

The `noir config init` command and other commands that create configuration files fail when the `~/.config` directory does not exist. This is because the `Dir.mkdir` function used is not recursive, preventing the creation of the necessary nested directories. The fix involves using a recursive directory creation method like `Dir.mkdir_p`.

This issue reports a bug where horizontal tables in the console component are rendering with unintended top borders for specific styles like 'box', 'double-box', and 'markdown'. Other table styles, such as 'borderless' and 'compact', do not exhibit this problem.

The parser incorrectly allows keywords like 'nil', 'true', 'false', and 'def' to be used as variable names within type declarations. This is a bug because these keywords are invalid identifiers and lead to unexpected behavior and errors when attempting to use these declared variables.

This issue proposes implementing the sending of the `minecraft:brand` payload through plugin channels in the Rosegold project. This involves protocol-level work to ensure correct packet IDs and field layouts for various Minecraft versions, sending the payload at the appropriate game lifecycle point, and verifying its implementation with byte-level serialization and integration tests.

This issue proposes adding a player radar feature, but the CivMC policy prohibits exposing entity data to bot logic. The implementation should focus on using server-provided tab-list information and avoid any features that could be used for bot automation or external program functionality.

The Spark Java detector incorrectly identifies Apache Spark data processing jobs as the Spark Java web framework due to a simplistic substring match. The issue proposes using a more precise regular expression to distinguish between the two, ensuring accurate detection of the Spark Java web framework.

This issue requests the addition of unit test specifications for several Python and Java web framework detectors. The goal is to create spec files that verify the functionality of these detectors, ensuring they correctly identify the presence of Bottle, Quart, Robyn, Javalin, Dropwizard, Micronaut, and Quarkus in codebases. The issue provides examples of the expected file structure and test case format.

This issue requests the addition of unit test specifications for seven Go framework detectors. The goal is to create spec files for Hertz, Huma, GoFrame, Goyave, go-restful, Connect, and PocketBase, mirroring the structure of existing Go detector specs. Each new spec should include at least one positive and one negative test case to ensure the detectors accurately identify the presence of these frameworks.

This issue requests the removal of redundant `size > 0` checks in the `nestjs.cr` file. These checks are always true because `String#scan` with a block always returns a `Regex::MatchData` object, which has a size of at least 1. The task involves simplifying conditional statements and trailing conditions in the specified file.

This issue proposes removing redundant `if match.size > 0` checks in the `tanstack_router.cr` file. These checks are always true because `String#scan` with a regex always returns a `Regex::MatchData` object with a size of at least 1. The task involves deleting these unnecessary guards and their corresponding `end` keywords.

This enhancement request proposes allowing users to configure Invidious to use privacy-friendly alternatives for external links like Reddit, Instagram, Twitter, and Wikipedia. Currently, Invidious links directly to these services, which can compromise user privacy. The proposed solution is to enable users to choose between the original service, or a privacy-focused instance like Teddit or Libreddit.

This bug prevents multiple users from subscribing to the same playlist. When a second user attempts to subscribe, a 'duplicate key value violates unique constraint' error occurs, indicating a database-level issue with how playlist subscriptions are being handled. This suggests a problem with the uniqueness constraint on the playlist subscription mechanism.

This issue proposes adding experimental HTTP/2 support to the Kemal web framework. While Crystal's standard HTTP server defaults to HTTP/1.1, HTTP/2 offers significant performance benefits. The issue highlights an existing native HTTP/2 implementation for Crystal and provides a working example, though it notes a current limitation in the `http2` shard.

This issue proposes to make the detection and handling of expectation matches outside of spec examples a built-in feature of the `Spec` module. Currently, such occurrences can lead to unhandled exceptions that halt spec execution. The goal is to provide a more structured output and prevent these unexpected failures.

This issue proposes removing redundant `match.size > 0` checks within the `koa.cr` analyzer. These checks are always true because `Regex::MatchData#size` will always be at least 1, as demonstrated by the provided example. The goal is to simplify the code by deleting these unnecessary guards without altering the output of endpoint and parameter extraction.

This issue proposes renaming the `golang_spec.cr` file to `golang_lexer_spec.cr` to align with the naming convention of other lexer specification files within the `spec/unit_test/minilexer/` directory. The goal is to maintain consistency and alphabetical ordering with other spec files, without altering the source file or its require paths.

This issue proposes removing redundant `match.size > 0` checks within the `express.cr` file. These checks are always true because `Regex::MatchData#size` will always be at least 1. The task involves deleting these unnecessary guards and adjusting the code structure accordingly, ensuring no functional changes to endpoint or parameter output.

This issue proposes removing redundant `match.size > 0` checks in the `restify.cr` file. These checks are always true because `Regex::MatchData#size` will always be at least 1, as it includes the full match. The goal is to simplify the code without changing its functionality or output.

The user wants to add 'HMooneyPot' as an alias for 'Invidious' within the `src/invidious.cr` file. This change is considered potentially difficult due to its impact on a core file and has a bounty attached.

This issue proposes implementing `sslmode=verify-full` for database connections, particularly for users connecting to Azure and CockroachLabs databases using the `cleartext` authentication method. The goal is to enhance security by ensuring full SSL certificate verification for these common use cases.

A bug report indicates that Crystal's HTTP client fails to automatically decompress gzip responses larger than approximately 13.8kb. The issue occurs when the server sends a gzipped response, and the client expects automatic decompression, but instead receives raw binary data for larger payloads.

This issue requests the addition of a functional tester for the Vercel specification analyzer. Currently, Vercel is the only analyzer lacking an end-to-end functional test, which verifies the detector, analyzer, and endpoint list on a real `vercel.json` file. The task involves creating a new fixture file and a corresponding tester file, modeled after existing Netlify tests.

This issue requests a code refactoring to replace `if !x.nil?` with the more idiomatic `unless x.nil?` in six specific locations within the codebase. This change is a straightforward syntactic improvement and does not alter the program's logic or behavior. The issue explicitly excludes compound conditions and `elsif` statements from this task.

This issue proposes adding a dedicated unit test for the `prefix_covers?` helper function within the `PrefixScope` module. Currently, this function's behavior is only tested indirectly through its usage in various framework taggers. The goal is to create a standalone spec file to directly verify its logic, particularly its handling of edge cases like partial string matches.

This issue requests the addition of four missing rows to a documentation table that maps v1 CLI flags to their v0 equivalents. The missing rows pertain to the `--pvalue` family of flags, specifically for the `cookie`, `form`, `json`, and `path` types, which are currently not documented in the flag consolidation table.

This issue requests the documentation of the `--no-spinner` flag for the `noir scan` command. The flag is functional but missing from the "Running" page's flag table on the documentation site. The task involves adding a new row for this flag to the English and Korean versions of the "Running" page's flag table.

This issue proposes replacing inefficient `Hash#values.includes?` calls with the more performant `Hash#has_value?` method in the JavaScript and Ktor extractors. This change aims to optimize performance by avoiding unnecessary array allocations within loops, as `Hash#has_value?` provides a direct and efficient way to check for value existence. The issue explicitly excludes one instance where `region.values` is an Array, for which `.includes?` is the correct method.

The `Token#to_s` method currently modifies the token's internal `@value` by escaping newlines and tabs, which is an unintended side effect for a formatting method. The fix involves computing the display form locally without altering the original `@value` and adopting the idiomatic Crystal `to_s(io)` signature.

This issue proposes removing 41 redundant `if match.size > 0` guards in the `js_route_extractor.cr` file. The `match.size` property of a `Regex::MatchData` object in Crystal is always at least 1 when a match is found, making these guards unnecessary and purely ceremonial.

This issue proposes to correct the location of two spec files for PHP and C# lexers. Currently, `php_lexer_spec.cr` and `csharp_lexer_spec.cr` are located in `spec/unit_test/miniparser/` instead of the correct `spec/unit_test/minilexer/` directory, following the project's structure convention. The fix involves a simple file move using `git mv`, with no changes required to the `require` statements within the files.