Migrate from `sprig` (`slim-sprig`) to `sprout`?

[andreynering]

sprig is the library that we use for template functions. We forked it on slim-sprig because the original imports too many packages and also had many functions that do not make sense for a template (crypto functions, etc).

Today, I learned that there's an attempt fork sprig given it hasn't had any activity for over 2 years:

• https://github.com/Masterminds/sprig/issues/396
• https://github.com/42atomys/sprout/issues/1
• https://github.com/42atomys/sprout

It's far from ready, but I decided to open this issue so we don't forget to take a look on how's the fork going in the near future.

[42atomys]

Hi again 👋,

Thank you again for your interest in https://github.com/go-sprout/sprout !

Given the impact of your suggestions on the loading of functions and loading only the functions you need, I have created an RFC about the loading strategy (load per package, load per function, load per import for build time).

Your input could be incredibly valuable for both of us: Sprout could develop a robust loading system, and you would have something similar to your slim-sprig library. Let's build something together 🥇

Best regards 🌱

[42atomys]

Hi @andreynering, after few weeks of work, the registry system (loader) are done with Release v0.5.0: Sprout Growth 🌿.

I will open a PR to implement the migration on go-task soon™ to test it 🚀

Thank you for your patience 🌱