You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with 5.4.0, Cell will no longer allow write access to paths in $/, both to improve sandboxing and ensure third-party tool scripts can't break out-of-source builds by building things directly inside the source tree. This is particularly important because Cell builds in-source, in $/dist, by default--it would be far too easy to break the out-of-source case and not realize it until it was too late to refactor.
There may or may not be cases where writing to specific files in the source tree is desirable, however. If these cases are common enough, it would be nice to have a function, we'll call it FS.unlock(), that could be called to unlock these files and enable them to be written to. It should not be possible to unlock the entire source tree, but unlocking whole subdirectories (for cases where an exact set of files isn't known in advance) could be useful. To discourage abuse, it also shouldn't be possible to unlock on demand--if FS.unlock() is called during execution of a tool, once the build proper has already begun, an error would be thrown. It needs to be called during initial Cellscript evaluation, while the build graph is still being constructed.
Note that this feature, if implemented, wouldn't be available until miniSphere 6.0 at the earliest.
The text was updated successfully, but these errors were encountered:
Starting with 5.4.0, Cell will no longer allow write access to paths in
$/
, both to improve sandboxing and ensure third-party tool scripts can't break out-of-source builds by building things directly inside the source tree. This is particularly important because Cell builds in-source, in$/dist
, by default--it would be far too easy to break the out-of-source case and not realize it until it was too late to refactor.There may or may not be cases where writing to specific files in the source tree is desirable, however. If these cases are common enough, it would be nice to have a function, we'll call it
FS.unlock()
, that could be called to unlock these files and enable them to be written to. It should not be possible to unlock the entire source tree, but unlocking whole subdirectories (for cases where an exact set of files isn't known in advance) could be useful. To discourage abuse, it also shouldn't be possible to unlock on demand--ifFS.unlock()
is called during execution of a tool, once the build proper has already begun, an error would be thrown. It needs to be called during initial Cellscript evaluation, while the build graph is still being constructed.Note that this feature, if implemented, wouldn't be available until miniSphere 6.0 at the earliest.
The text was updated successfully, but these errors were encountered: