restify 2.0.2 → 2.1.0

data/vendor/bundle/ruby/4.0.0/gems/json-2.19.9/README.md

@@ -0,0 +1,310 @@
+# JSON implementation for Ruby
+
+[![CI](https://github.com/ruby/json/actions/workflows/ci.yml/badge.svg)](https://github.com/ruby/json/actions/workflows/ci.yml)
+
+## Description
+
+This is an implementation of the JSON specification according to RFC 7159
+http://www.ietf.org/rfc/rfc7159.txt .
+
+The JSON generator generate UTF-8 character sequences by default.
+If an :ascii\_only option with a true value is given, they escape all
+non-ASCII and control characters with \uXXXX escape sequences, and support
+UTF-16 surrogate pairs in order to be able to generate the whole range of
+unicode code points.
+
+All strings, that are to be encoded as JSON strings, should be UTF-8 byte
+sequences on the Ruby side. To encode raw binary strings, that aren't UTF-8
+encoded, please use the to\_json\_raw\_object method of String (which produces
+an object, that contains a byte array) and decode the result on the receiving
+endpoint.
+
+## Installation
+
+Install the gem and add to the application's Gemfile by executing:
+
+    $ bundle add json
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+    $ gem install json
+
+## Basic Usage
+
+To use JSON you can
+
+```ruby
+require 'json'
+```
+
+Now you can parse a JSON document into a ruby data structure by calling
+
+```ruby
+JSON.parse(document)
+```
+
+If you want to generate a JSON document from a ruby data structure call
+```ruby
+JSON.generate(data)
+```
+
+You can also use the `pretty_generate` method (which formats the output more
+verbosely and nicely) or `fast_generate` (which doesn't do any of the security
+checks generate performs, e. g. nesting deepness checks).
+
+## Casting non native types
+
+JSON documents can only support Hashes, Arrays, Strings, Integers and Floats.
+
+By default if you attempt to serialize something else, `JSON.generate` will
+search for a `#to_json` method on that object:
+
+```ruby
+Position = Struct.new(:latitude, :longitude) do
+  def to_json(state = nil, *)
+    JSON::State.from_state(state).generate({
+      latitude: latitude,
+      longitude: longitude,
+    })
+  end
+end
+
+JSON.generate([
+  Position.new(12323.234, 435345.233),
+  Position.new(23434.676, 159435.324),
+]) # => [{"latitude":12323.234,"longitude":435345.233},{"latitude":23434.676,"longitude":159435.324}]
+```
+
+If a `#to_json` method isn't defined on the object, `JSON.generate` will fallback to call `#to_s`:
+
+```ruby
+JSON.generate(Object.new) # => "#<Object:0x000000011e768b98>"
+```
+
+Both of these behavior can be disabled using the `strict: true` option:
+
+```ruby
+JSON.generate(Object.new, strict: true) # => Object not allowed in JSON (JSON::GeneratorError)
+JSON.generate(Position.new(1, 2)) # => Position not allowed in JSON (JSON::GeneratorError)
+```
+
+## JSON::Coder
+
+Since `#to_json` methods are global, it can sometimes be problematic if you need a given type to be
+serialized in different ways in different locations.
+
+Instead it is recommended to use the newer `JSON::Coder` API:
+
+```ruby
+module MyApp
+  API_JSON_CODER = JSON::Coder.new do |object, is_object_key|
+    case object
+    when Time
+      object.iso8601(3)
+    else
+      object
+    end
+  end
+end
+
+puts MyApp::API_JSON_CODER.dump(Time.now.utc) # => "2025-01-21T08:41:44.286Z"
+```
+
+The provided block is called for all objects that don't have a native JSON equivalent, and
+must return a Ruby object that has a native JSON equivalent.
+
+It is also called for objects that do have a JSON equivalent, but are used as Hash keys, for instance `{ 1 => 2}`,
+as well as for strings that aren't valid UTF-8:
+
+```ruby
+coder = JSON::Combining.new do |object, is_object_key|
+  case object
+  when String
+    if !string.valid_encoding? || string.encoding != Encoding::UTF_8
+      Base64.encode64(string)
+    else
+      string
+    end
+  else
+    object
+  end
+end
+```
+
+## Combining JSON fragments
+
+To combine JSON fragments into a bigger JSON document, you can use `JSON::Fragment`:
+
+```ruby
+posts_json = cache.fetch_multi(post_ids) do |post_id|
+  JSON.generate(Post.find(post_id))
+end
+posts_json.map! { |post_json| JSON::Fragment.new(post_json) }
+JSON.generate({ posts: posts_json, count: posts_json.count })
+```
+
+## Round-tripping arbitrary types
+
+> [!CAUTION]
+> You should never use `JSON.unsafe_load` nor `JSON.parse(str, create_additions: true)` to parse untrusted user input,
+> as it can lead to remote code execution vulnerabilities.
+
+To create a JSON document from a ruby data structure, you can call
+`JSON.generate` like that:
+
+```ruby
+json = JSON.generate [1, 2, {"a"=>3.141}, false, true, nil, 4..10]
+# => "[1,2,{\"a\":3.141},false,true,null,\"4..10\"]"
+```
+
+To get back a ruby data structure from a JSON document, you have to call
+JSON.parse on it:
+
+```ruby
+JSON.parse json
+# => [1, 2, {"a"=>3.141}, false, true, nil, "4..10"]
+```
+
+Note, that the range from the original data structure is a simple
+string now. The reason for this is, that JSON doesn't support ranges
+or arbitrary classes. In this case the json library falls back to call
+`Object#to_json`, which is the same as `#to_s.to_json`.
+
+It's possible to add JSON support serialization to arbitrary classes by
+simply implementing a more specialized version of the `#to_json method`, that
+should return a JSON object (a hash converted to JSON with `#to_json`) like
+this (don't forget the `*a` for all the arguments):
+
+```ruby
+class Range
+  def to_json(*a)
+    {
+      'json_class'   => self.class.name, # = 'Range'
+      'data'         => [ first, last, exclude_end? ]
+    }.to_json(*a)
+  end
+end
+```
+
+The hash key `json_class` is the class, that will be asked to deserialise the
+JSON representation later. In this case it's `Range`, but any namespace of
+the form `A::B` or `::A::B` will do. All other keys are arbitrary and can be
+used to store the necessary data to configure the object to be deserialised.
+
+If the key `json_class` is found in a JSON object, the JSON parser checks
+if the given class responds to the `json_create` class method. If so, it is
+called with the JSON object converted to a Ruby hash. So a range can
+be deserialised by implementing `Range.json_create` like this:
+
+```ruby
+class Range
+  def self.json_create(o)
+    new(*o['data'])
+  end
+end
+```
+
+Now it possible to serialise/deserialise ranges as well:
+
+```ruby
+json = JSON.generate [1, 2, {"a"=>3.141}, false, true, nil, 4..10]
+# => "[1,2,{\"a\":3.141},false,true,null,{\"json_class\":\"Range\",\"data\":[4,10,false]}]"
+JSON.parse json
+# => [1, 2, {"a"=>3.141}, false, true, nil, 4..10]
+json = JSON.generate [1, 2, {"a"=>3.141}, false, true, nil, 4..10]
+# => "[1,2,{\"a\":3.141},false,true,null,{\"json_class\":\"Range\",\"data\":[4,10,false]}]"
+JSON.unsafe_load json
+# => [1, 2, {"a"=>3.141}, false, true, nil, 4..10]
+```
+
+`JSON.generate` always creates the shortest possible string representation of a
+ruby data structure in one line. This is good for data storage or network
+protocols, but not so good for humans to read. Fortunately there's also
+`JSON.pretty_generate` (or `JSON.pretty_generate`) that creates a more readable
+output:
+
+```ruby
+ puts JSON.pretty_generate([1, 2, {"a"=>3.141}, false, true, nil, 4..10])
+ [
+   1,
+   2,
+   {
+     "a": 3.141
+   },
+   false,
+   true,
+   null,
+   {
+     "json_class": "Range",
+     "data": [
+       4,
+       10,
+       false
+     ]
+   }
+ ]
+```
+
+There are also the methods `Kernel#j` for generate, and `Kernel#jj` for
+`pretty_generate` output to the console, that work analogous to Core Ruby's `p` and
+the `pp` library's `pp` methods.
+
+## Security
+
+When parsing or serializing untrusted input, parser and generator options should never be user controlled.
+
+```ruby
+# Dangerous, DO NOT DO THIS.
+JSON.generate(params[:data], params[:options])
+```
+
+Security vulnerability reports relying on attacker controlled parsing or generator options will be handled as regular bug fixes.
+
+## Development
+
+### Prerequisites
+
+1. Clone the repository
+2. Install dependencies with `bundle install`
+
+### Testing
+
+The full test suite can be run with:
+
+```bash
+bundle exec rake test
+```
+
+### Release
+
+Update the `lib/json/version.rb` file.
+
+```
+rbenv shell 2.6.5
+rake build
+gem push pkg/json-2.3.0.gem
+
+rbenv shell jruby-9.2.9.0
+rake build
+gem push pkg/json-2.3.0-java.gem
+```
+
+## Author
+
+Florian Frank <mailto:flori@ping.de>
+
+## License
+
+Ruby License, see https://www.ruby-lang.org/en/about/license.txt.
+
+## Download
+
+The latest version of this library can be downloaded at
+
+* https://rubygems.org/gems/json
+
+Online Documentation should be located at
+
+* https://www.rubydoc.info/gems/json
+
+[Ragel]: http://www.colm.net/open-source/ragel/

data/vendor/bundle/ruby/4.0.0/gems/language_server-protocol-3.17.0.5/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 Fumiaki MATSUSHIMA
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/vendor/bundle/ruby/4.0.0/gems/language_server-protocol-3.17.0.5/README.md

@@ -0,0 +1,88 @@
+# LanguageServer::Protocol
+
+A Language Server Protocol SDK for Ruby.
+
+[![Gem Version](https://badge.fury.io/rb/language_server-protocol.svg)](https://badge.fury.io/rb/language_server-protocol)
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'language_server-protocol'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install language_server-protocol
+
+## Usage
+
+Currently, this gem supports only stdio as transport layer out of box.
+
+```ruby
+require "language_server-protocol"
+
+LSP = LanguageServer::Protocol
+writer = LSP::Transport::Stdio::Writer.new
+reader = LSP::Transport::Stdio::Reader.new
+
+subscribers = {
+  initialize: -> {
+    LSP::Interface::InitializeResult.new(
+      capabilities: LSP::Interface::ServerCapabilities.new(
+        text_document_sync: LSP::Interface::TextDocumentSyncOptions.new(
+          change: LSP::Constant::TextDocumentSyncKind::FULL
+        ),
+        completion_provider: LSP::Interface::CompletionOptions.new(
+          resolve_provider: true,
+          trigger_characters: %w(.)
+        ),
+        definition_provider: true
+      )
+    )
+  }
+}
+
+reader.read do |request|
+  result = subscribers[request[:method].to_sym].call
+  writer.write(id: request[:id], result: result)
+  exit
+end
+```
+
+You can use any IO object as transport layer:
+
+```ruby
+io = StringIO.new
+writer = LSP::Transport::Io::Writer.new(io)
+reader = LSP::Transport::Io::Reader.new(io)
+```
+
+## Versioning
+
+language_server-protocol gem does NOT use semantic versioning.
+This gem versions are structured as `x.y.z.t`.
+`x.y.z` indicates the [Language server protocol](https://github.com/Microsoft/language-server-protocol/) version and `t` is a monotonically increasing number.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/mtsmfm/language_server-protocol-ruby. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the LanguageServer::Protocol project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/mtsmfm/language_server-protocol-ruby/blob/main/CODE_OF_CONDUCT.md).

data/vendor/bundle/ruby/4.0.0/gems/lint_roller-1.1.0/CHANGELOG.md

@@ -0,0 +1,15 @@
+## [Unreleased]
+
+## [1.1.0]
+
+- Add `LintRoller::Support` module of classes designed to make it a little
+easier to author plugins. `MergesUpstreamMetadata#merge` will allow a minimal
+YAML config (say, `standard-sorbet`'s, which only contains `Enabled` values for
+each rule) to merge in any other defaults from a source YAML (e.g.
+`rubocop-sorbet`'s which includes `Description`, `VersionAdded`, and so on).
+This way that metadata is neither absent at runtime nor duplicated in a standard
+plugin that mirrors a rubocop extension
+
+## [1.0.0]
+
+- Initial release

data/vendor/bundle/ruby/4.0.0/gems/lint_roller-1.1.0/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2023 Test Double, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/vendor/bundle/ruby/4.0.0/gems/lint_roller-1.1.0/README.md

@@ -0,0 +1,173 @@
+# lint_roller - A plugin specification for linters
+
+`lint_roller` is an itty-bitty plugin API for code analysis tools like linters
+and formatters. It provides plugins for those tools to load extensions and
+specify custom rulesets.
+
+(As of this release, only [Standard
+Ruby](https://github.com/standardrb/standard) supports `lint_roller` plugins,
+but we think [RuboCop](https://github.com/rubocop/rubocop) could add support and
+most plugins would be compatible with both `rubocop` and `standardrb`.
+Additionally, there's nothing that would prevent other tools like
+[rufo](https://github.com/ruby-formatter/rufo) from adopting it.)
+
+## How to make a plugin
+
+If you want to make a plugin, the first thing you should do is extend
+[LintRoller::Plugin](/lib/lint_roller/plugin.rb) with a custom class. Let's take
+this example plugin for banana-related static analysis:
+
+```ruby
+module BananaRoller
+  class Plugin < LintRoller::Plugin
+    # `config' is a Hash of options passed to the plugin by the user
+    def initialize(config = {})
+      @alternative = config["alternative"] ||= "chocolate"
+    end
+
+    def about
+      LintRoller::About.new(
+        name: "banana_roller",
+        version: "1.0", # or, in a gem, probably BananaRoller::VERSION
+        homepage: "https://github.com/example/banana_roller",
+        description: "Configuration of banana-related code"
+      )
+    end
+
+    # `context' is an instance of LintRoller::Context provided by the runner
+    def supported?(context)
+      context.engine == :rubocop
+    end
+
+    # `context' is an instance of LintRoller::Context provided by the runner
+    def rules(context)
+      LintRoller::Rules.new(
+        type: :path,
+        config_format: :rubocop,
+        value: Pathname.new(__dir__).join("../../config/default.yml")
+      )
+    end
+  end
+end
+```
+
+And that's pretty much it. Just a declarative way to identify your plugin,
+detect whether it supports the given
+[LintRoller::Context](/lib/lint_roller_context.rb) (e.g. the current `runner`
+and `engine` and their respective `_version`s), for which the plugin will
+ultimately its configuration as a [LintRoller::Rules](/lib/lint_roller/rules.rb)
+object.
+
+## Packaging a plugin in a gem
+
+In order for a formatter to use your plugin, it needs to know what path to
+require as well as the name of the plugin class to instantiate and invoke.
+
+To make this work seamlessly for your users without additional configuration of
+their own, all you need to do is specify a metadata attribute called
+`default_lint_roller_plugin` in your gemspec.
+
+Taking [standard-custom](https://github.com/standardrb/standard-custom) as an
+example, its gemspec contains:
+
+```ruby
+Gem::Specification.new do |spec|
+  # …
+  spec.metadata["default_lint_roller_plugin"] = "Standard::Custom::Plugin"
+  # …
+end
+```
+
+Because gem specs are loaded by RubyGems and Bundler very early, remember to
+specify the plugin as a string representation of the constant, as load order
+usually matters, and most tools will need to be loaded before any custom
+extensions. Hence, `"Standard::Custom::Plugin"` instead of
+`Standard::Custom::Plugin`.
+
+## Using your plugin
+
+Once you've made your plugin, here's how it's configured from a Standard Ruby
+`.standard.yml` file.
+
+### If your plugin is packaged as a gem
+
+Packaging your plugin in a gem is the golden path, both because distributing
+code via [RubyGems.org](https://rubygems.org) is very neat, but also because it
+makes the least work for your users.
+
+If your gem name is `banana_roller` and you've set
+`spec.metadata["default_lint_roller_plugin"]` to `"BananaRoller::Plugin"`, then
+your users could just add this to their `.standard.yml` file:
+
+```yaml
+plugins:
+  - banana_roller
+```
+
+And that's it! During initialization, `standardrb` will `require
+"banana_roller"` and know to call `BananaRoller::Plugin.new(config)` to
+instantiate it.
+
+### If your plugin ISN'T in a gem
+
+If you're developing a plugin for internal use or in conjunction with a single
+project, you may want it to live in the same repo as opposed to packaging it in
+a gem.
+
+To do this, then—in lieu of a gem name—provide the path you want to be required
+as its name, and (since there is no `spec.metadata` to learn of your plugin's
+class name), specify it as an option on the plugin:
+
+```yaml
+plugins:
+  - lib/banana_roller/plugin:
+      plugin_class_name: BananaRoller::Plugin
+```
+
+(Be careful with the indentation here! Any configuration under a plugin must be
+indented in order for it to be parsed as a hash under the
+`"lib/banana_roller/plugin"` key.)
+
+Additionally, if you want the plugin's name to make more sense, you can give
+it whatever name you like in the configuration and specify the `require_path`
+explicitly:
+
+```yaml
+plugins:
+  - banana_roller:
+      require_path: lib/banana_roller/plugin
+      plugin_class_name: BananaRoller::Plugin
+```
+
+### Passing user configuration to the plugin
+
+When a `LintRoller::Plugin` is instantiated, users can pass a configuration hash
+that tells your plugin how to behave.
+
+To illustrate how this works in Standard Ruby, anything passed as a hash beneath
+a plugin will be passed to the class's `initialize` method:
+
+```yaml
+plugins:
+  - apple_roller
+  - banana_roller:
+      require_path: lib/banana_roller/plugin
+      plugin_class_name: BananaRoller::Plugin
+      alternative: "apples"
+  - orange_roller:
+      rind: false
+```
+
+In the above case, `apple_roller`'s plugin class will be instantiated with
+`new({})`, `banana_roller` will get all 3 of those parameters passed
+`BananaRoller::Plugin.new({require_path…})`, and `orange_roller`'s class will be
+called with `new({rind: false})`.
+
+## Code of Conduct
+
+This project follows Test Double's [code of
+conduct](https://testdouble.com/code-of-conduct) for all community interactions,
+including (but not limited to) one-on-one communications, public posts/comments,
+code reviews, pull requests, and GitHub issues. If violations occur, Test Double
+will take any action they deem appropriate for the infraction, up to and
+including blocking a user from the organization's repositories.