I apologize if that’s the wrong section of the forums, I couldn’t find one dedicated to packages in general so treat this as a question about ECS packages specifically.
Let’s assume a case where I find a bug or need a small feature implemented. With traditional assets imported into the main project structure, that was a matter of modifying project files directly and registering changes in version control. Packages, however, are read-only and hosted strictly in a special Unity folder detached from any projects, outside of version control view. What is the proper workflow for editing them?
Based on roadmap from Unite, I’m assuming that the end game is forking the entire package repository, working on changes through a local clone of that fork, pushing them and distributing the updated result through the upcoming Git or NPM integrations? While that’s in development, what’s the second best solution? Carving out isolated parts of the package like Unity.Transforms folder, moving them whole into your project, editing their namespace to something like Unity.Transforms.Fork and referencing that in your scripts?