googlesamples / googlesamples/unity-jar-resolver

Add support for moving Unity package files to canonical install locations in VersionHandler

Open
#193 0 comments 0 reactions 0 assignees View on GitHub
type: feature request
Dominant language
C#
Stars
1.5k
Forks
371
Avg merge
14h 21m
Merged PRs (30d)
3

Description

Some plugins want to move files about in Unity packages and Unity seems to require moving components into folders to upload to the asset store (see https://github.com/googlesamples/unity-jar-resolver/issues/190 )

Since importing multiple plugins with the same transitive dependencies at different versions when each version is imported at a different path is problematic (see https://github.com/googlesamples/unity-jar-resolver#unity-plugin-version-management ), then perhaps adding the option to have the Version Handler detect plugin files at unintended install locations and move them to the intended locations when it runs would workaround this issue.

For example, if a plugin contains the file:

* myplugin/myplugin.dll

and it's included in another plugin at:

* someotherplugin/myplugin/myplugin.dll

when the Version Handler runs it could detect the moved file and move it into the install location i.e `myplugin/myplugin.dll` instead.

The install location of a file could be stored in either the version handler manifest file (see https://github.com/googlesamples/unity-jar-resolver#version-handler-usage ) or applied as a label to each file.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.