Closed VRspace4 closed 8 years ago
I'm not 100% sure what you mean here.
Is this a caching problem in the browser (as we spoke about in Gitter), or something else.
However, if 900-custom.json is changed to the following (removed src/ from core_custom.css line):
This would fail, beacuse the path is invalid.
The path resolution appears to be different for grunt build script and OS.js. At the moment, I have 900-config.json
with the following (without src/
) because only then the custom style would work even with the error message from grunt core
:
//900-custom.json
{
"stylesheets": [
"src/client/stylesheets/core.css",
"src/client/stylesheets/gui.css",
"client/dprm/themes/core_custom.css"
]
}
I'll try this locally
Your file is stored how exactly (path relative to OS.js) ?
C:\dev\OS.js\src\client\dprm\themes\core_custom.css
Do a pull, then set the file back to src/client/dprm/themes/core_custom.css
and run
grunt core dist-files
The update works. Thanks!
Solved in 1a90bb7ca8228a9c468b8c0dffabc024866c0780
Sure thing!
Expected behaviour
When the following is added into
900-custom.json
to override core css's withcore_custom.css
:It's expected the
grunt core
command to execute without any errors AND the splash screen and progress bar reflects the custom colors defined in thecore_custom.css
.Actual behaviour
With the addition specified above to
900-custom.json
,grunt core
command executes fine, but the custom css doesn't take effect.However, if
900-custom.json
is changed to the following (removedsrc/
fromcore_custom.css
line):the splash screen and progress bar does take effect but
grunt core
command would fail with the following output: