It appears in my dependencies on VSCode like this:
It appears as lowercase, which isn't ideal, but it doesn't affect my ability to use it. It does affect my ability to select my local development version as a path, though.
To Reproduce
Steps to reproduce the behavior:
Right click the "kass" dependency
Select "Use Local Version"
Navigate to folder (potentially named "Kass") with Kass inside and select it
See error:
'kass': package at '{/path/to}/Kass' is Kass but was expecting kass
Expected behavior
The local version should be selected.
Environment
OS: macOS Sonoma 14.6.1
Swift version (output of swift --version)
swift-driver version: 1.90.11.1 Apple Swift version 5.10 (swiftlang-5.10.0.13 clang-1500.3.9.4)
Target: arm64-apple-macosx14.0
It seems like this issue is related to this one which was recently moved from this project over to swift package manager. I'm currently looking into this!
Describe the bug
I'm currently developing my reverse-engineering toolkit, Kass on my device in a folder named
Kass
(uppercase K). The package itself is also named with an uppercase K, which I think is the actual causal contribution to this.I have a package in a separate folder I use for testing it as a library, pulling in the latest
main
via myPackage.swift
like so:It appears in my dependencies on VSCode like this:
It appears as lowercase, which isn't ideal, but it doesn't affect my ability to use it. It does affect my ability to select my local development version as a path, though.
To Reproduce Steps to reproduce the behavior:
Expected behavior The local version should be selected.
Environment
swift --version
)Additional context It seems the VSCode plugin is running this command behind the scenes:
If I instead run this command myself, it works fine (and I can use my local development version):
I'm not sure why the plugin lowercases dependency names to begin with, but it seems to be the root cause of this issue.