Crystal good first issues

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 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.

This issue proposes merging two duplicate spec files for `Noir::ScalaLexer` into a single, consolidated file. The goal is to eliminate redundancy, ensure all test cases are covered in one place, and maintain a clear structure that mirrors the source code organization.

This issue proposes the removal of a 93-line dead code method, `extract_handler_params_from_content`, from the Restify JavaScript analyzer in `src/analyzer/analyzers/javascript/restify.cr`. The method is defined but never called, and its only potential caller is in a separate Express analyzer class. The issue also notes a subtle bug in the dead code related to regex matching.

This issue involves removing three unused private methods from the C# ASP.NET Core MVC analyzer. These methods were superseded by changes made when Minimal API support was extracted into a separate file and are no longer called by any active code. The task is to delete these specific methods without altering other parts of the codebase.

This issue proposes refactoring duplicated s-expression scanning logic across five Clojure analyzers into a single `Analyzer::Clojure::Helper` module. The goal is to eliminate redundant code by creating a shared helper file and updating the existing analyzers to use it, ensuring functional parity.

This enhancement issue proposes the removal of unused and duplicated code within the Invidious codebase. The reporter has identified specific examples of unused variables, functions, and arguments that can be safely deleted without impacting functionality.

This issue requires updating outdated language and framework counts in the project's README and documentation. The current numbers are significantly stale, and the task involves regenerating the authoritative list, recounting the supported technologies, and then updating all instances across the documentation and README files to reflect the accurate, current figures.

This issue proposes consolidating seven duplicated private methods named `extract_python_string` across different Python analyzers into a single method within the `Analyzer::Python::Helper` module. The goal is to reduce code duplication and improve maintainability by having a single source of truth for this functionality.

This issue requests the addition of unit tests for the Noir::ScalaLexer. Currently, only two out of five mini-lexers have dedicated unit tests, and the Scala lexer is only indirectly tested. The goal is to create a new spec file for the Scala lexer, mirroring the structure of existing tests and covering its public methods with various test cases, including specific edge cases related to Scala syntax.

This issue reports that CLI error messages are being colorized yellow, making them indistinguishable from warning messages. The fix involves changing the colorization of specific error messages from yellow to red to align with the established color convention for errors.

This issue proposes to replace instances of `.size == 0` and `.size != 0` with the more idiomatic `.empty?` and `!empty?` respectively in the codebase. The change applies to `String` and `Array` types and is a straightforward refactoring with no behavioral changes.

This issue requests documentation updates for the Noir CLI's export and webhook flags. Specifically, it asks to add `--export-opensearch`, `--export-webhook`, and `--tls-skip-verify` to the 'Deliver Results to Other Tools' page, including a flag table and usage examples. The documentation should also clarify the purpose and security implications of `--tls-skip-verify`.