Results for: "partition"

Response class for Expectation Failed responses (status code 417).

The server cannot meet the requirements of the Expect request-header field.

References:

Response class for Variant Also Negotiates responses (status code 506).

Transparent content negotiation for the request results in a circular reference.

References:

Map from option/keyword string to object with completion.

Raises when ambiguously completable string is encountered.

Raises when switch is undefined.

No documentation available

This represents a location in the source.

No documentation available

BasicSpecification is an abstract class which implements some common code used by both Specification and StubSpecification.

Base exception class for RubyGems. All exception raised by RubyGems are a subclass of this one.

No documentation available

Raised by Gem::Resolver when a Gem::Dependency::Conflict reaches the toplevel. Indicates which dependencies were incompatible through conflict and conflicting_dependencies

Potentially raised when a specification is validated.

Used to raise parsing and loading errors

No documentation available

Raised by the DependencyInstaller when a specific gem cannot be found

No documentation available
No documentation available

Represents an error communicating via HTTP.

Raised by Gem::Validator when something is not right in a gem.

Raised by Gem::WebauthnListener when an error occurs during security device verification.

The Specification class contains the information for a gem. Typically defined in a .gemspec file or a Rakefile, and looks like this:

Gem::Specification.new do |s|
  s.name        = 'example'
  s.version     = '0.1.0'
  s.licenses    = ['MIT']
  s.summary     = "This is an example!"
  s.description = "Much longer explanation of the example!"
  s.authors     = ["Ruby Coder"]
  s.email       = 'rubycoder@example.com'
  s.files       = ["lib/example.rb"]
  s.homepage    = 'https://rubygems.org/gems/example'
  s.metadata    = { "source_code_uri" => "https://github.com/example/example" }
end

Starting in RubyGems 2.0, a Specification can hold arbitrary metadata. See metadata for restrictions on the format and size of metadata items you may add to a specification.

No documentation available
No documentation available

Gem::StubSpecification reads the stub: line from the gemspec. This prevents us having to eval the entire gemspec in order to find out certain information.

Search took: 8ms  ·  Total Results: 3065