Fix current and parent directory paths for gems

[ahukkanen]

• Tests written and linted ℹ︎
• Documentation written ℹ︎
• Commit history is tidy ℹ︎

What this does

Given you have the following Gemfile:

# frozen_string_literal: true

source "https://rubygems.org"

git_source(:github) { |repo_name| "https://github.com/#{repo_name}" }

ruby "2.7.3"

gem "current-path-gem", "0.1.0", path: "."
gem "parent-path-gem", "0.1.0", path: ".."

This produces the following Gemfile.lock:

PATH
  remote: ..
  specs:
    parent-path-gem (0.1.0)

PATH
  remote: .
  specs:
    current-path-gem (0.1.0)

GEM
  remote: https://rubygems.org/
  specs:

PLATFORMS
  x86_64-linux

DEPENDENCIES
  current-path-gem (= 0.1.0)!
  parent-path-gem (= 0.1.0)!

RUBY VERSION
   ruby 2.7.3p183

BUNDLED WITH
   2.2.19

The gemfile package does not identify the paths for the current and parent path when the path definition does not have a / character in it.

Notes for the reviewer

See the added Gemfile lock for reference what this is about.

More information

N/A

Screenshots

N/A

[CLAassistant]

All committers have signed the CLA.