Bug description
The meta file for ResolverUtilities.cs is missing in the respository, rendering it unusable as a directly hooked up package via the Package Manager.
Repro steps
- Create a new Unity Project.
- Add MessagePack via the Package Manager:
"Add Package from git URL"
https://github.com/neuecc/MessagePack-CSharp.git?path=src/MessagePack.UnityClient/Assets/Scripts/MessagePack
Expected behavior
It should work and compile just fine!
Actual behavior
Instead I am greeted with the following message:
Asset Packages/com.neuecc.messagepack/Resolvers/ResolverUtilities.cs has no meta file, but it's in an immutable folder. The asset will be ignored.
And thus
Library\PackageCache\com.neuecc.messagepack@3e624b9499\Resolvers\DynamicObjectResolver.cs(114,55): error CS0103: The name 'ResolverUtilities' does not exist in the current context
Additional context
Yes the installation via the .unitypackage works fine, but I do prefer the usage of the Package Manager which makes updating the asset a lot more convenient.
Bug description
The meta file for ResolverUtilities.cs is missing in the respository, rendering it unusable as a directly hooked up package via the Package Manager.
Repro steps
Expected behavior
It should work and compile just fine!
Actual behavior
Instead I am greeted with the following message:
Asset Packages/com.neuecc.messagepack/Resolvers/ResolverUtilities.cs has no meta file, but it's in an immutable folder. The asset will be ignored.And thus
Library\PackageCache\com.neuecc.messagepack@3e624b9499\Resolvers\DynamicObjectResolver.cs(114,55): error CS0103: The name 'ResolverUtilities' does not exist in the current contextAdditional context
Yes the installation via the
.unitypackageworks fine, but I do prefer the usage of the Package Manager which makes updating the asset a lot more convenient.