The first plugin version record is unreliable, especially as plugins are added and removed; so this commit stores the first boot date in the database explicitly by using a database migration.
This ensures that the mix:compile command returns the correct exit codes based on the status of the compilation. It also adds the following option flags to `mix:compile`:
- `--silent`: Runs the compilation process silently without outputting any details from Webpack / Mix
- `--stop-on-error`: Exits the compilation if an error is encountered
- `--manifest`: Defines the package.json file to be used for the compilation
The no-plusplus rule is less than ideal as it prevents using a useful language feature without providing adequate justification (see https://airbnb.io/javascript/#variables--unary-increment-decrement for original justification).
Prior to this commit the eslint configuration did not allow for:
```js
++something
something++
--something
something--
```
Relative path is generated from $this->assetPath which is by default null. Changing it to be an empty string by default instead would have consequences further down the line in the CombineAssets class.
Fixes an issue where the version number reported by the database wasn't normalized causing issues when comparing with the normalized version from the filesystem.
If you need to use the CMS Controller's Twig instance then you should call getTwig() directly on the controller instance instead of relying upon twig.environment.cms being a singleton.
It being a singleton causes issues if for some reason you want to render another route in the same request as the second call to Controller->run() will pollute the variables of the first.
This fixes#578 by adding the ability to pass the CMS Controller instance to the CMS Twig Extension removing the reliance on context variables as well as making the expected "global" twig variables inside of the CMS Twig environment actually global within that environment.
Replaces #598 & #593.
Credit to @RomainMazB for the initial implementation.
This implements support for the ImageResizer within the media manager for thumbnail resizing & image cropping. This simplifies and centralizes the image resizing code within the media manager and allows for better support on readonly filesystems by relying on the ImageResizer class to process image modification requests.
Matches the behavior of the ViewMaker in the 1.1 branch more closely by checking if the partial path is a local reference first, returning that path if it is. Only if this check fails will it then run through the view paths.
Fixes https://github.com/wintercms/winter/issues/571
Also fixes the ViewMaker tests by emulating the same behaviour as a web request and having the current directory be the base path of the site, not the directory of the current module or plugin being tested.
