Create hls-plugin-api and move plugins to exe#379
Conversation
2b97604 to
f650d75
Compare
|
Maybe add a |
pepeiborra
left a comment
There was a problem hiding this comment.
This is great! Definitely a step in the right direction. Eventually we can move the current plugins into separate packages too, as needed.
Mmm i like to put the main logic in the library like f.e. dhall, if it does not introduce extraneous dependencies. |
|
ci nix build failed with: 🤔 |
Nix uses |
Ailrun
left a comment
There was a problem hiding this comment.
Great! I had planned to do this but couldn't find an enough time slot...
Thank you for extracting plugin API!
|
@alanz @pepeiborra i dont feel |
That sounds fine to me! |
|
I agree. The So in future I would imagine a person writing say a formatter and including a plugin descriptor directly, and the formatter depends on |
The log says it's building |
Oops, i forgot to put them when moving the deps around, thanks! |
|
Ok, the executable modules are in the lib now and ci is happy (thanks again @georgefst) |
47f1029 to
83571f0
Compare
|
Rebased, i hope this could be merged asap, cause it will likely be in conflict with any other commit, as it shuffles almost all modules in the project |
83571f0 to
678b4d5
Compare
678b4d5 to
af69f89
Compare
* Require shake-0.18.4 which contains actionBracket * Change progress reporting to use files rather than Shake nodes * Remove inadvertantly writing down Shake twice
The second one would be the hls-plugin-api and the second one the exe component in this pr.
Not sure about:
builtininsteaddefault?