2013-04-08 15:35:22 -04:00
|
|
|
#!/usr/bin/env bats
|
|
|
|
|
|
|
|
load test_helper
|
|
|
|
|
|
|
|
setup() {
|
|
|
|
mkdir -p "$RBENV_TEST_DIR"
|
|
|
|
cd "$RBENV_TEST_DIR"
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "reports global file even if it doesn't exist" {
|
|
|
|
assert [ ! -e "${RBENV_ROOT}/version" ]
|
|
|
|
run rbenv-version-origin
|
|
|
|
assert_success "${RBENV_ROOT}/version"
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "detects global file" {
|
|
|
|
mkdir -p "$RBENV_ROOT"
|
|
|
|
touch "${RBENV_ROOT}/version"
|
|
|
|
run rbenv-version-origin
|
|
|
|
assert_success "${RBENV_ROOT}/version"
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "detects RBENV_VERSION" {
|
|
|
|
RBENV_VERSION=1 run rbenv-version-origin
|
|
|
|
assert_success "RBENV_VERSION environment variable"
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "detects local file" {
|
|
|
|
touch .ruby-version
|
|
|
|
run rbenv-version-origin
|
|
|
|
assert_success "${PWD}/.ruby-version"
|
|
|
|
}
|
|
|
|
|
|
|
|
@test "detects alternate version file" {
|
|
|
|
touch .rbenv-version
|
|
|
|
run rbenv-version-origin
|
|
|
|
assert_success "${PWD}/.rbenv-version"
|
|
|
|
}
|
create hook: version-origin
Expose a `version-origin` hook.
It is invoked *before* the traditional `rbenv-version-file` lookup. Because `version-origin` is traditionally run immediately after `version-name`, then any plugin hooks that alter `version-name` would have done so. Thus, running `version-origin` prior to printing the origin gives those plugins a chance to alter the `version-origin` to match.
If any of the hooks set `$RBENV_VERSION_ORIGIN`, then it is used as the return value. Otherwise, the existing logic continues to return "environment variable" or "filename" as appropriate.
This change, in conjunction with the `version-name` hook, makes a clean seam by which plugins can inject their own ruby version setting logic. Using this seam, as opposed to altering `$RBENV_COMMAND_PATH` from the `which` hook, means that the version name and origin are set more reliably and so `version`, `version-name`, `version-origin` and `which` all work as expected. Indeed, even PS1 works now.
2015-05-27 23:29:11 -04:00
|
|
|
|
|
|
|
@test "reports from hook" {
|
2015-12-23 11:32:21 -05:00
|
|
|
mkdir -p "${RBENV_ROOT}/rbenv.d/version-origin"
|
|
|
|
cat > "${RBENV_ROOT}/rbenv.d/version-origin/test.bash" <<HOOK
|
|
|
|
RBENV_VERSION_ORIGIN=plugin
|
|
|
|
HOOK
|
create hook: version-origin
Expose a `version-origin` hook.
It is invoked *before* the traditional `rbenv-version-file` lookup. Because `version-origin` is traditionally run immediately after `version-name`, then any plugin hooks that alter `version-name` would have done so. Thus, running `version-origin` prior to printing the origin gives those plugins a chance to alter the `version-origin` to match.
If any of the hooks set `$RBENV_VERSION_ORIGIN`, then it is used as the return value. Otherwise, the existing logic continues to return "environment variable" or "filename" as appropriate.
This change, in conjunction with the `version-name` hook, makes a clean seam by which plugins can inject their own ruby version setting logic. Using this seam, as opposed to altering `$RBENV_COMMAND_PATH` from the `which` hook, means that the version name and origin are set more reliably and so `version`, `version-name`, `version-origin` and `which` all work as expected. Indeed, even PS1 works now.
2015-05-27 23:29:11 -04:00
|
|
|
|
2015-12-23 11:32:21 -05:00
|
|
|
RBENV_VERSION=1 RBENV_HOOK_PATH="${RBENV_ROOT}/rbenv.d" run rbenv-version-origin
|
create hook: version-origin
Expose a `version-origin` hook.
It is invoked *before* the traditional `rbenv-version-file` lookup. Because `version-origin` is traditionally run immediately after `version-name`, then any plugin hooks that alter `version-name` would have done so. Thus, running `version-origin` prior to printing the origin gives those plugins a chance to alter the `version-origin` to match.
If any of the hooks set `$RBENV_VERSION_ORIGIN`, then it is used as the return value. Otherwise, the existing logic continues to return "environment variable" or "filename" as appropriate.
This change, in conjunction with the `version-name` hook, makes a clean seam by which plugins can inject their own ruby version setting logic. Using this seam, as opposed to altering `$RBENV_COMMAND_PATH` from the `which` hook, means that the version name and origin are set more reliably and so `version`, `version-name`, `version-origin` and `which` all work as expected. Indeed, even PS1 works now.
2015-05-27 23:29:11 -04:00
|
|
|
assert_success "plugin"
|
|
|
|
}
|
2015-12-23 11:26:53 -05:00
|
|
|
|
|
|
|
@test "doesn't inherit RBENV_VERSION_ORIGIN from environment" {
|
|
|
|
RBENV_VERSION_ORIGIN=ignored run rbenv-version-origin
|
|
|
|
assert_success "${RBENV_ROOT}/version"
|
|
|
|
}
|