silverstripe-framework/.gitignore

/assets/
.sass-cache
.DS_Store
npm-debug.log
/.buildpath
/.project
/.settings
node_modules/
coverage/
/**/*.js.map
/**/*.css.map
/vendor/
composer.lock
silverstripe-cache/
Ignore assets dir that can be created on dev/build 2018-09-29 23:52:08 +02:00			`/assets/`
FEATURE: initial cut of the template and styles for DataGrid 2011-09-28 05:06:06 +02:00			`.sass-cache`
ENHANCEMENT Renamed DataGrid to GridField 2011-09-30 00:59:44 +02:00			`.DS_Store`
Adds npm for managing client-side dependencies - Includes a package.json file with build and CI scripts - Includes shrinkwrap file for locking dependency version - Includes Gulp for running build tasks - Includes a 'build' task for copying library files from node_modules to thirdparty - Includes a 'sanity' task for makes sure library files in thirdparty match what's in node_modules - Includes updates to .travis.yml (new JS_SANITY_CHECK flag) to run the sanity task 2016-01-06 04:06:47 +01:00			`npm-debug.log`
added ignore 2012-02-18 03:26:15 +01:00			`/.buildpath`
			`/.project`
			`/.settings`
Adds npm for managing client-side dependencies - Includes a package.json file with build and CI scripts - Includes shrinkwrap file for locking dependency version - Includes Gulp for running build tasks - Includes a 'build' task for copying library files from node_modules to thirdparty - Includes a 'sanity' task for makes sure library files in thirdparty match what's in node_modules - Includes updates to .travis.yml (new JS_SANITY_CHECK flag) to run the sanity task 2016-01-06 04:06:47 +01:00			`node_modules/`
CampaignAdmin and GridField React sections Also removes watchify because it wasn't working. Add SilverStripeBackend class used to fetch data from endpoints for the front-end 2016-03-16 01:30:39 +01:00			`coverage/`
Consolidated bundles, sourcemaps and watching We don't want a bundle for each section, unnecessary network overhead and too much boilerplate in defining build tooling. 2016-03-23 22:34:14 +01:00			`/*/.js.map`
API Use Webpack The bundle is generated by running “webpack” directly - gulp is no longer needed as an intermediary. The resulting config is a lot shorter, although more configuration is pushed into lib.js. Modules are shared between javascript files as global variables. Although this global state pollution is a bit messy, I don’t think it’s practically any worse than the previous state, and it highlights the heavy coupling between the different packages we have in place. Reducing the width of the coupling between the core javascript and add-on modules would probably be a better way of dealing with this than replacing global variables with some other kind of global state. The web pack execution seems roughly twice as fast - if I clear out my framework/client/dist/js folder, it takes 13.3s to rebuild. However, it’s not rebuilding other files inside dist, only the bundle files. CSS files are now included from javascript and incorporated into bundle.css by the webpack. Although the style-loader is helpful in some dev workflows (it allows live reload), it introduces a flash of unstyled content which makes it inappropriate for production. Instead ExtractTextPlugin is used to write all the aggregated CSS into a single bundle.css file. A style-loader-based configuration could be introduced for dev environments, if we make use of the webpack live reloader in the future. Note that the following features have been removed as they don't appear to be necessary when using Webpack: - UMD module generation - thirdparty dist file copying LeftAndMain.js deps: Without it, ssui.core.js gets loaded too late, which leads e.g. to buttons being initialised without this added behaviour. 2016-08-21 03:17:50 +02:00			`/*/.css.map`
ENHANCEMENT Allow vendor modules with url rewriting API Introduce ModuleResource feature 2017-09-21 07:54:06 +02:00			`/vendor/`
NEW: Don’t set up SilverStripe project for test run The SilverStripe project structure complicates the travis test run, and the goal of this branch is to prevent it from being necessary. - Unit tests can be run simply with PHPUnit. - Behat test can be run with the silverstripe/serve module Note that initially this commit doesn’t cater to the behat tests. As part of this, we allow dev packages to be installed when testing These settings don’t affect projects that use framework, only when framework’s composer install / require calls are used themselves. Since SS4 is pre-stable, these are important. They can probably be removed once SS4 stable (and stable versions of support packages) have been released. 2016-09-12 07:42:05 +02:00			`composer.lock`
			`silverstripe-cache/`