mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-06-29 16:09:23 +02:00
9c3feb4ab4
At current certain interfaces exist that assume only local assets will be loaded (e.g. `SilverStripe\Forms\HTMLEditor\TinyMCEConfig::getConfig()`), where as someone may wish to load an off site resource via the use of an absolute URL (e.g. for fontawesome css provided via a CDN). Because asset path parsing is filtered through a `SilverStripe\Core\Manifest\ResourceURLGenerator`, one must either know in advance if they want an internal or external resource (loading different generators), or the API must allow for this (i.e. an inclusion function for each type of asset). So we can either double the API on the implementing class, or simply make an exception for an absolute URL as high as possible; inside the filter - for which the `vendor/module : path/to/file.asset` shorthand syntax was specifically designed not to conflict with. |
||
|---|---|---|
| _config | ||
| .github | ||
| .tx | ||
| client | ||
| docs | ||
| lang | ||
| src | ||
| templates | ||
| tests | ||
| thirdparty | ||
| _config.php | ||
| _register_database.php | ||
| .codecov.yml | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .scrutinizer.yml | ||
| .travis.yml | ||
| .upgrade.yml | ||
| behat.yml | ||
| cli-script.php | ||
| composer.json | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| phpcs.xml.dist | ||
| phpunit.xml.dist | ||
| README.md | ||
| sake | ||
| silverstripe_version | ||
SilverStripe Framework
PHP5 framework forming the base for the SilverStripe CMS (http://silverstripe.org).
Requires a silverstripe-installer base project. Typically used alongside the cms module.
Installation
See installation on different platforms, and installation from source.
Bugtracker
Bugs are tracked on github.com. Please read our issue reporting guidelines.
Development and Contribution
If you would like to make changes to the SilverStripe core codebase, we have an extensive guide to contributing code.