Will Osborne
Will Osborne
## Feature Request ### Description of Problem: Currently spectral rules check that referenced interfaces are defined. It does not check that they're defined on the specified node - so this...
## Feature Request Add a new ruleset to validate pattern files, with the same functionality as the existing one (which only supports instantiations). ### Description of problem Currently we have...
## Feature Request Once CLI is ready we need to ensure all validations, spectral + JSON Schema, are run against patterns and samples in the repo whenever something changes. Combined...
## Bug Report ### Steps to Reproduce: Add a boolean field to a node, relationship or metadata object e.g. ```json { "type": "object", "properties": { "propertyBoolean": { "type": "boolean" }...
## Feature Request ### Description of Problem: Currently the different commands have some inconsistencies in their usage that may be confusing to users. For example, the validate command uses -m...
## Feature Request ### Description of Problem: Currently when generate is run, it spits out a file with placeholders for missing values: - `{{ PLACEHOLDER }}` for strings - `-1`...
## Bug Report Running the CALM CLI on my machine gives me the following warning: ``` (node:15726) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead....
## Feature Request ### Description of Problem: Currently validation report is output as a JSON object. We have a --format flag that lets you optionally set JUnit for XML output,...
## Feature Request ### Description of Problem: The CALM CLI bundles the meta-schemas it was built against alongside the app. When a user tries to generate/validate a pattern, these schemas...
## Feature Request ### Description of Problem: Currently some of the errors output by the commands are confusing. e.g. running the 'calm validate' command with **no arguments** produces a large...