cli issueshttps://gitlab.entropy.cc/blacklight-cms/cli/-/issues2020-10-07T14:01:59Zhttps://gitlab.entropy.cc/blacklight-cms/cli/-/issues/2Blacklight on Windows, CLI commands fail2020-10-07T14:01:59ZAaron HarderBlacklight on Windows, CLI commands failModule installation, mkdirp and symlink creation both seem to fail on Windows.
- Possibly you need to use `mklink \D shared ..\..\blacklight_modules\fshr\shared\apps` when on Windows?
+ But why doesn't `fs.symlink()` adapt itself p...Module installation, mkdirp and symlink creation both seem to fail on Windows.
- Possibly you need to use `mklink \D shared ..\..\blacklight_modules\fshr\shared\apps` when on Windows?
+ But why doesn't `fs.symlink()` adapt itself properly to the OS?
- What's up with mkdirp not working?
And once you get past that:
- How about ImageMagick and the other img-opt utils?
- Do all /tmp/ folder, etc work as expected?https://gitlab.entropy.cc/blacklight-cms/cli/-/issues/3Blacklight Testing Framework2020-10-07T14:01:57ZCaleb WeeksBlacklight Testing FrameworkTests should be executable via the command line tool. Should optionally be able to specify a moduleId, a test suit id, and a use case id
<code>
bl test
bl test &lt;module_id&gt;
bl test &lt;module_id&gt; &lt;suite_id&gt; &lt;use_case_i...Tests should be executable via the command line tool. Should optionally be able to specify a moduleId, a test suit id, and a use case id
<code>
bl test
bl test <module_id>
bl test <module_id> <suite_id> <use_case_id>
eg: bl test blacklight.edit image-widget query-for-image
</code>Caleb WeeksCaleb Weekshttps://gitlab.entropy.cc/blacklight-cms/cli/-/issues/7Allow BL modules to be NPM modules2020-10-07T14:02:06ZCaleb WeeksAllow BL modules to be NPM modules# Current Behavior
Blacklight modules have to be pulled in via GIT.
# New Behavior
Allow Blacklight modules to be installed from NPM modules
## Implementation
This will entail a pretty significant enhancement to the CLI module-builder...# Current Behavior
Blacklight modules have to be pulled in via GIT.
# New Behavior
Allow Blacklight modules to be installed from NPM modules
## Implementation
This will entail a pretty significant enhancement to the CLI module-builder.installModule command. Should look for an `npm` property on the module in the site config. The value of the `npm` property is expected to be the name of the NPM module.
Once the identified, all that the cli should need to do is resolve the path to that module (`require.resolve(npmValue)`) then create a symlink from the relevant location in the blacklight_modules directory to the resolved npm path. If resolving the npm path throws an exception that should be thrown all the way to the top of the cli command.
We'll need to verify that the subsequent linking in the `bl module relink` command continues to work as expected.Caleb WeeksCaleb Weekshttps://gitlab.entropy.cc/blacklight-cms/cli/-/issues/8Parallelize module commands2019-09-18T17:39:39ZCory BryantParallelize module commandsAdd support for running module commands (install, exec, etc) in parallel, with a max concurrency setting.
@aaron.harder @caleb.weeksAdd support for running module commands (install, exec, etc) in parallel, with a max concurrency setting.
@aaron.harder @caleb.weeks