Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Resolver is baffled by projects with an all lowercase /assets/ folder name #83

Open
owlboy opened this issue Feb 3, 2023 · 0 comments
Labels
bug Something isn't working vpm-resolver Issues related to the VPM Package Resolver package

Comments

@owlboy
Copy link

owlboy commented Feb 3, 2023

Describe the bug
When loading Resolver in a project with an Assets folder named assets the Resolver fails to load properly.

To Reproduce
Steps to reproduce the behavior:

Rename /MyProject/Assets/ to /MyProject/assets/ and observe errors in the console relating to ResolverWindow.cs.

Expected behavior
The Resolver should function.

Screenshots
image

Desktop (please complete the following information):

  • macOS
  • 12.6 (21G115)

Additional context
This was discovered and discussed in the green server. @ScruffyRules helped discover the cause of the errors.

When I fixed the capitalization the project opened without any discernible issues. So having the SDK fix it automatically at some point should be fine. A warning from the SDK would be welcome if an automatic fix is not feasible.

@Faxmashine Faxmashine added bug Something isn't working Resolver labels Mar 28, 2023
@orels1 orels1 added vpm-resolver Issues related to the VPM Package Resolver package and removed Resolver labels May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working vpm-resolver Issues related to the VPM Package Resolver package
Projects
None yet
Development

No branches or pull requests

3 participants