SilverStripe 4+ support
Closed this issue · 3 comments
We should introduce SilverStripe 4 support, my thoughts on this is that we no longer provide a language plugin that includes the SilverStripe core modules but instead we add the vendor folder as the library path. That way we no longer need to supply the updated library but still function as normal. We'll need some kind of logic that looks outside the current project to attempt to find the vendor folder, for modules and themes it should only be two up. For the app/mysite project it should only be one up. Perhaps one way we find it is to A: limit the depth to look up the directory tree and B: look for the composer.lock as a verification step along with the vendor/silverstripe/framework folder existing. This should then be stored.
- New Language Library Lookup Style based on finding the vendor folder
- New Templates for SilverStripe 4
- Bump PDT version requirement to support
DataObject::classand not throw errors
We should also have the tests view not work in SilverStripe 4+ projects as that UI is not available in 4+.
For module projects we'll need to come up with a way to include the vendor folder but not include the project itself.
done