-
Notifications
You must be signed in to change notification settings - Fork 299
Open
Description
Using SimpleJSON in custom packages either results in
- including the files unchanged, meaning that it will break when it is added to projects containing other packages that do this
- including the files, but appending your namespace to the SimpleJSON namepace. this prevents collisions, but the json types in one namespace can't be converted to the same json types in another namspace without serializing the objects to a string and deserializing them back to an object.
- using one of the unofficial forks which are often severely desynchronised from the main repo
My proposed solutions are
- Convert the SimpleJSON repo into a Unity Package (unlikely)
- Add a branch to the SimpleJSON repo which contains the Unity Package (tricky to move changes from main branch to package branch)
- Create an entire new repo for the Unity Package, and clone the SimpleJSON repo into a folder named
Runtime/SimpleJSON. Add a.gitignorefile to the SimpleJSON repo ignoring any*.metafiles. When changes are made to SimpleJSON, they can be pulled to the repo inside the Unity Package repo, then the Unity Package can push those changes to it's own repo.
ijovi23
Metadata
Metadata
Assignees
Labels
No labels