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

Projeny validation fails when paths are involved #85

Open
decden opened this issue Aug 14, 2018 · 2 comments
Open

Projeny validation fails when paths are involved #85

decden opened this issue Aug 14, 2018 · 2 comments

Comments

@decden
Copy link
Contributor

decden commented Aug 14, 2018

Hello

I am trying to configure a projeny project. I however always get a "Projeny validation failed" error when opening the generated project with unity.

I had a look at the validation function in the projeny.dll source code, and it seems to me like it expects everything in Assets/* and Assets/Plugins/* to be a junction. For me this is not the case since:

  • I use PluginsFolder: MyApp/MyPlugins in my ProjenyProject.yaml, causing the Assets/MyApp/MyPlugins folder to be created (which is not a junction)
  • I have dependencies of the form MyRepository/General/MyPlugin, which also cause the directory to appear at top level in Assets (again, not as junction).

Another detail which might be important is that I define the PackageFolders as '[ProjectRoot]/../../../'

At this point I am wondering why the project creation succeeded, but the validation failed. Am I using Projeny wrong, or is the validation not aligned to the directory layouts projeny can produce?

Thanks in advance for your help.

@decden decden changed the title Projeny validation Fails when paths are involved Projeny validation fails when paths are involved Aug 14, 2018
@svermeulen
Copy link
Contributor

Projeny was written with the assumption that the values given to PluginsFolder: and AssetsFolder: are package names and not paths. Which is why it assumes that all the junctions should be directly under Assets and Plugins

@decden
Copy link
Contributor Author

decden commented Aug 16, 2018

Thanks for the hints. I have restructured my project, so that I no longer use paths for PluginsFolder, AssetsFolder and Dependencies and the validation now succeeds.

It would be nice though to get an error/warning during project creation instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants