Skip to content

Check for unsupported guard version during require #2

Description

@e2

Since Guard::Compat no longer has a dependency on guard, it can have a "weak dependency" by checking the version in guard/compat.rb (e.g. when automatically required by Bundler) - if there is a guard version available, it check if it's ok.

This would at least give a better error for issues like: guard/guard-rspec#312

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions