- Issue created by @tstoeckler
- π¨π¦Canada Charlie ChX Negyesi πCanada
You are now a maintainer of pax. Please open a new branch and submit the module into there. A better implementation is welcome. No need for a new project. The current pax implementation is not worth maintaining if there's a better solution.
- π©πͺGermany tstoeckler Essen, Germany
Awesome, thanks very much for the quick response!
Just because I would regret not having asked: Are you married to the
pax
namespace? I just personally don't find it the most intuitive name (but maybe there's something I'm missing?), so I wouldn't mind just claiming theconfig_shard
namespace anyway and then we can both be maintainers over there. But it's not a big deal either way and if you prefer staying here that's also totally fine and I will just open a new branch here. - π¨π¦Canada Charlie ChX Negyesi πCanada
If you can make upgrade work feel free to sunset this module and recommend config_shard instead. Likely it needs two deployments, the first installs config_shard and the second removes pax. I can't see it working in a single step. This, of course, would require config_shard being able to read pax sharded config dirs. It's very likely the upgrade is just documentation.
What I really want to avoid is having two modules for the same purpose especially when one is a dirty unmaintained hack. Which name they live under, I couldn't care less.
- π©πͺGermany tstoeckler Essen, Germany
Nice, yeah I will try that then. Yeah, sounds good, should be manageable regarding the update path ποΈ
- π¨π¦Canada Charlie ChX Negyesi πCanada
Since I edited my comment above, let me repeat: it's very likely the upgrade is just documentation. It just needs to be written and tested -- manually. No need for a phpunit test for that. Thanks for modernizing this.
- π©πͺGermany tstoeckler Essen, Germany
Right, makes sense. No worries, thanks for the idea!
- π¨π¦Canada Charlie ChX Negyesi πCanada
Since this module won't see a D11 upgrade now and also it's quite hard to uninstall a module which has been removed, I asked in #contribute how to proceed and the best I got was to release a new version with a hook requirements message to note this is the last version. Could you release another D10 module here with that?
- π©πͺGermany tstoeckler Essen, Germany
Yes, that totally makes sense. Will do that!