Sha256: c5bebd45f150db6dbea52a07157832ad6e48a2172c1b1579a22a6b6fcdfe8fc8
Contents?: true
Size: 1.52 KB
Versions: 5
Compression:
Stored size: 1.52 KB
Contents
Feature: Version constraint In order to use Vim plugins which are compatible with my configuration, as a lazy Vim user, I want to declare desirable versions of Vim plugins. Note that vim-flavor assumes that plugins follow [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html), to determine compatibility of plugins. See also [Philosophy](../philosophy) for the details. Background: Given a repository "foo" with versions "1.0 1.1 1.2 2.0" Scenario: Declare using the latest version of a Vim plugin Given a flavorfile with: """ruby flavor '$foo_uri' """ When I run `vim-flavor install` Then it should pass And a lockfile is created with: """ $foo_uri (2.0) """ And a flavor "$foo_uri" version "2.0" is deployed to "$home/.vim" Scenario: Declare using a Vim plugin not older than a specific version Given a flavorfile with: """ruby flavor '$foo_uri', '>= 1.1' """ When I run `vim-flavor install` Then it should pass And a lockfile is created with: """ $foo_uri (2.0) """ And a flavor "$foo_uri" version "2.0" is deployed to "$home/.vim" Scenario: Declare using the latest and compatible version of a Vim plugin Given a flavorfile with: """ruby flavor '$foo_uri', '~> 1.0' """ When I run `vim-flavor install` Then it should pass And a lockfile is created with: """ $foo_uri (1.2) """ And a flavor "$foo_uri" version "1.2" is deployed to "$home/.vim"
Version data entries
5 entries across 5 versions & 1 rubygems