1.1.5 (1.1 Update 5)

Fixes issue discovered with some base template references to items not included in the serialization coming through and blowing up the generation.

1.1.4 (1.1 Update 4)

Adds new Solution Statistics Feature (#29) that provides some high-level statistics about the solution on the Project, Layer and Module models, and can be used to take a quick temperature check of the solution's technical debt/helix adherence.

1.1.3 (1.1 Update 3)

• Fixes issue with validation errors for the foundation layer incorrectly being added to the feature layer
• Fixes some bugs with the TeamCity meta runner not correctly displaying the help text or name of the Options Data field, and added quotes to support paths with spaces in the names

1.1.2 (1.1 Update 2)

Improves validation error messages to be prefixed by "INVALID:" and to include the paths of the source and target templates of the offending dependency

1.1.1 (1.1 Update 1)

• Fixes bug that was preventing code from displaying dependencies from one template on another in the same module on the module templates dependencies and module templates dependents diagrams. This issue appears to have existed in all versions >=1.0.0 as well (#49)
• Fixes bug wherein a dependency model separate from the (already created) inheritance (generalization) model was being created instead of just reusing the inheritance model. It was also because of the use of the dependency model vs the generalization model that the stereotype for the template had to be cleared, resulting in the "Box Display" for templates. As such, this also eliminates the need to have the Box Display in the documentation (#49)

1.1.0 (1.1 Initial Release)

• Updates RabbitMQ AMQP middleman to read JSON options data (i.e. the DocumentationConfiguration object and CompletionHandler array) from a file instead of reading the data in from command line, as the command line was causing side-effects when trying to parse the JSON string. A workaround for this issue had been added in 1.1.0-rc2 (use   in place of spaces and pass a true parameter at the end to tell the middleman to replace with spaces) but this fix was hacky and not effective enough.

1.1.0-rc2 (1.1 Release Candidate 2)

• Updates completion handlers to expect a Params object instead of a Params array
• Fixes an issue with metaball parameter missing from ABS and S3 handler _execute function signatures (#43)
• Adds support for passing in a DocumentationConfiguration object to extend the one sent from the serializer and changes the completion handlers argument to be an options argument (#45)
• Adds a workaround to the RabbitMQ middleman for PowerShell issue that doesn't allow spaces to be included into the JSON string passed in as an argument, by adding an optional additional argument that, if true, will replace   instances with spaces
• Updates the TeamCity MetaRunner to support new updates to the RabbitMQ middleman, as well as updates the inline documentation displayed to the user to match the changes (#45, #43)

1.1.0-rc1 (1.1 Release Candidate 1)

Adds support for new MS Teams notifications completion handler

1.1.0-rc0 (1.1 Release Candidate 0)

• Adds new dependency validation features that color invalid dependencies red on diagrams
• Adds support for passing validation errors along with a new "metaball" object to completion handlers, enabling users to write more robust logic to handle the completion state of the generation
• Adds new Slack Integration support, enabling users to create a webhook to their Slack workspaces that will notify them after any SitecoreDXG build and will list out any dependency validation errors that were encountered

1.0.0 (1.0 Initial Release)

Initial public release.

Only change from 0.beta.15 was an arbitrary change to the package.json description for the Generation service that was made for consistency