Currently, code dependencies (PHP/JS libraries) are "shipped/stored" within the official repository (ie. PHP SDK for AWS, RSS parser, file API...) and are manually upgraded.
It could be convenient to handle those with some tools, like :
potentially allow less "reinvent the wheel" in favor of relying on appropriate/well established libraries
Drawbacks :
pulling dependencies that way usually means a lot of "garbage" is also pulled (documentation, unit tests, minified versions...), which means that would make Revo heavier, unless we develop some kind of "cleaning" mechanism (ie. remove x/y folders after pulling/upgrading dependencies)
This won't bring anything fancy or new to users/developers, besides having more up to date deps.
Currently, code dependencies (PHP/JS libraries) are "shipped/stored" within the official repository (ie. PHP SDK for AWS, RSS parser, file API...) and are manually upgraded.
It could be convenient to handle those with some tools, like :
Benefits :
Drawbacks :
This won't bring anything fancy or new to users/developers, besides having more up to date deps.