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
Currently the build package uses the sde-prep directory as a "working directory" and writes the preprocessed mdl file (the output of sde generate --preprocess) to that directory. If the mdl file directly references other external data files, then these file references won't work because the mdl file is now at a different level than the data files. For example:
The following is an example of an mdl file and a project directory structure that doesn't currently work:
The workaround for now is to use one of the config file callbacks to edit the paths so that data.csv is replaced with ../model-files/data.csv.
The ext-control-params integration test is affected by this issue. Here's an example of how to change the config file to apply the above workaround (taken from the sde.config.js file for that test):
plugins: [// XXX: Include a custom plugin that applies post-processing steps. This is// a workaround for issue #303 where external data files can't be resolved.{postProcessMdl: (_,mdlContent)=>{returnmdlContent.replaceAll('ext-control-params.csv','../ext-control-params.csv')}},
...
]
The text was updated successfully, but these errors were encountered:
Currently the
build
package uses thesde-prep
directory as a "working directory" and writes the preprocessed mdl file (the output ofsde generate --preprocess
) to that directory. If the mdl file directly references other external data files, then these file references won't work because the mdl file is now at a different level than the data files. For example:The following is an example of an mdl file and a project directory structure that doesn't currently work:
The workaround for now is to use one of the config file callbacks to edit the paths so that
data.csv
is replaced with../model-files/data.csv
.The
ext-control-params
integration test is affected by this issue. Here's an example of how to change the config file to apply the above workaround (taken from thesde.config.js
file for that test):The text was updated successfully, but these errors were encountered: