Open bertsky opened 4 years ago
eb1f7b634f36a3362f1564ada4e9ef31352fd95d is a first step.
These files contain comments as self-documentation, which itself is illegal JSON and can only work when supported by spec/core.
But how do we distribute them, so they can be easily integrated into workflows?
JSON comments are now allowed in the spec. Also, we now have processor resources as a mechanism to install presets. Must revisit.
eb1f7b634f36a3362f1564ada4e9ef31352fd95d is a first step.
These files contain comments as self-documentation, which itself is illegal JSON and can only work when supported by spec/core.
But how do we distribute them, so they can be easily integrated into workflows?