Some package.json attributes within Template archive need rethinking.

[Martin Halford]

Bug Report 🐛

The package.json contains some legacy artefacts which need to be removed or rethought.

Current Behaviour

An Accord Project template archive contains a package.json file containing the following definition:

    "accordproject": {
        "template": "clause",
        "cicero": "^0.24.0",
        "runtime": "ergo"
    },

The runtime attribute is redundant - should it be removed?

The template attribute seems to causes an error when using certain cicero commands (e.g. cicero archive), when it is set to contract - but the cicero commands seem to works fine when set to it is set to clause. It's probably still doing some sort of validation against the Ergo logic syntax - maybe?

Possible Solution

• Remove the template and runtime attributes completely - unless there is some benefit to keeping them for future use.

Context (Environment)

• cicero v0.24.0
• node v19.9.0

[Matt Roberts]

I made a start to this work in this PR.

[accordproject/cicero] Pull request opened: #786 BREAKING CHANGE(*): Remove dependency on Ergo. Remove Draft, Parse, Initialize, Trigger from API