Mark Scott
Mark Scott
#1493 briefly discussed this issue and agreed it is important. Knowing whether 'strict' mode can be enabled at a module level would be beneficial, as will moving some of the...
All metadata properties would be optional. I'm primarily proposing a standard place for 'CALM' ones to exist within `metadata`, with some potential examples. I agree on potential change from `schema`...
The current metadata type (core.json#/defs/metadata) is used at many places in the CALM schema. The `metadata` top level element is optional. If we are mandating `metadata/calm/schemaVersion` and `metadata/calm/type`, then this...
@jpgough-ms raised a point on #1493 that a top level `calm` key controlled in the CALM schema may be better than reserving a property 'by convention' in the metadata. If...
The problem here is that the pattern and architecture files are converted from string to object and. back to string before validation. The conversion from object to string is not...
Discussed at Office Hours - @markscott-ms will dig further into the code as to why there is serialization and deserialization going on. If it's possible to report line/column numbers, then...
Resolved by #1950
Mark Scott / Morgan Stanley
Mark Scott / Morgan Stanley
Discussed in #1798 . This PR makes protocol more extensible. It is a non-breaking change. Change protocol to be just a 'string', but agreed to include in release 1.1.