zkniebel/sitecoreuml

SitecoreUML is an architecture visualization tool that enables architects and developers to visualize existing Sitecore architectures in UML and to create, visualize and deploy new Sitecore template architectures directly from their UML diagrams. It even has the power to generate MSDN-style documentation for any Sitecore architecture!

sitecoreuml's Issues

Update add support for choosing which type of layout formatting should be used by default on generation

It would be nice if users could choose the default format type when generating their diagrams. By default, SitecoreUML currently auto-formats the diagrams. Instead, it would be great if this were based on preferences.

Connection Test feature does not display error modal when test fails

The Connection Test feature does not display an error message, popup, etc. if the test fails. Opening the DevTools console, I can see JavaScript errors occurred.

(Reported to me, directly, via Sitecore Slack - user wished to remain anonymous)

Add Template Exclude Paths to Module

In the upcoming features for v1.2 there is an entry for adding exclude paths support, as follows:

• Adds template exclude paths to SitecoreUML.config (paths to exclude when data is being imported into StarUML)

A request came in today to add support for this new feature prior to version 1.2.

Star UML extension is not working with latest Star UML

After installing latest Star UML extension for sitecore . Preferences tab doesn't have option for Sitecore. See screen shot

Define is not defined

Hi, I've installed everything but the extensions is not loading. If I inspect through devtools I'm getting this error:

C:\Program Files\StarUML\resources\app.asar\src\extensibility\extension-loader.js:205 [Extension] failed to load C:\Users\Esther\AppData\Roaming\StarUML\extensions\user\SitecoreUML ReferenceError: define is not defined
loadExtension @ C:\Program Files\StarUML\resources\app.asar\src\extensibility\extension-loader.js:205

Any ideas?

Paths in SitecoreUML.config are set to developer's absolute path and no instructions included in Installation documentation for updating them

The installation instructions do not mention that users must update the paths for the following configuration elements before they can use the module:

• importDropFolderPath
• importHistoryFolderPath
• exportSaveFolderPath

This causes issues when trying to use the module, and the manual configuration step is a pain.

Recommended fix is to change these elements to instead be configuration settings, so that the $(dataFolder) variable can be used. This will enable the developer to eliminate his local file paths from the configuration and will enable consumers of the module to install it without any additional configuration steps on their part.

This bug was mentioned to me by a colleague who hasn't told me whether or not I can post his name, yet.