svgbob

[elasticdotventures]

Close # ...

Changes proposed in this pull request:
...

I'm not at all sure if I've done this correctly. This syntax is very odd to me.

Please check...

• [x ] Files are formated with prettier
• [ x] New code is covered with unittests
• [ x] All unittests are passing
• [ x] All commits are semantic

[jontze]

Hey @elasticdotventures , thanks for your contribution and the feature request. The PR is code wise on a good way.

The actions relies on pre-compiled binaries that the project owner of a plugin attach as artifacts to the github releases. And while looking through the releases of the boozook/mdbook-svgbob repo I realized that there is only a single pre-release published (with pre-compiled binaries as artifacts). Sadly the action doesn't support pre-releases yet and therefore the implementation will not work atm, as there is only one release and that's a pre-release.

So I suggest that we create a feature request issue to add support for the svgbob mdbook plugin and another feature request to allow the usage pre-releases of plugins, as this will add some more input variables (probably for each plugin) to the action.

Another approach would be to encourage the author of the boozook/mdbook-svgbob project to publish a stable release on github, what would save us to implement support for unstable releases.

[jontze]

I'm closing this PR in favor of #299 and #298.