Don’t wanted to open an issue, because this is at first only a question:
The toolkit has (always!?) been a git submodule in the kirby git repository. As I updated my kirby repo, the toolkit submodule disappeared.
Is this a intended behavior?
Don’t wanted to open an issue, because this is at first only a question:
The toolkit has (always!?) been a git submodule in the kirby git repository. As I updated my kirby repo, the toolkit submodule disappeared.
Is this a intended behavior?
Yes, it’s intended. We now manage the toolkit dependency with composer. The submodule unfortunately made a couple problems and we felt that this is the more stable way to move forward.
Thanks for the answer.
But I think, I will keep my submodule structure for my existing projects and simply include the toolkit in my own git repo.
I’m currently trying to check out the permissions to replace my own/private permissions hack of the panel. I’m very excited.