@sabrish/power-platform-solution-blueprint 1.1.2 → 1.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +46 -0
- package/README.md +1 -1
- package/dist/assets/index-BSqcU9dy.js +3537 -0
- package/dist/index.html +1 -1
- package/npm-shrinkwrap.json +2 -2
- package/package.json +1 -1
- package/dist/assets/index-9ZM4ASzq.js +0 -3133
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,52 @@ All notable changes to Power Platform Solution Blueprint will be documented in t
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [1.4.0] — 2026-07-01
|
|
9
|
+
|
|
10
|
+
### Added
|
|
11
|
+
- **AI-friendly Markdown export — YAML frontmatter and flat headings** — all generated Markdown files now include YAML frontmatter blocks with metadata (`blueprint_type`, logical name, display name, counts, version); entity overview sections include Dataverse description as blockquote for self-contained AI agent reading; cross-entity trace sections replace `<details>`/`<summary>` HTML collapsed blocks with flat `###` headings so content is visible to AI agents and rendered expanded in ADO Wiki
|
|
12
|
+
|
|
13
|
+
### Changed
|
|
14
|
+
- **Markdown export headings in cross-entity trace** — replaced `<details>`/`<summary>` HTML collapsed sections with flat `###` headings (H3) for improved readability in AI agents and Azure DevOps Wiki rendering
|
|
15
|
+
|
|
16
|
+
### Technical
|
|
17
|
+
- **MarkdownFormatter new static helpers** — `formatFrontmatter(fields)` generates YAML with proper escaping (string quoting for colons/hashes/newlines, YAML 1.1 literal detection, array flow sequences with per-item escaping); `formatBlockquote(text)` handles multi-line blockquotes with proper indentation
|
|
18
|
+
- **`extractPublisherPrefix` refactoring** — moved 4th duplicate into `src/core/utils/entityName.ts` as named export; `MarkdownReporter.ts` imports it; pre-existing duplicates in `ERDGenerator.ts` and `SolutionDistributionAnalyzer.ts` tracked for follow-up consolidation
|
|
19
|
+
- **Version import consolidation** — both `MarkdownReporter.ts` and `JsonReporter.ts` now import `version` from `package.json` (matching pattern)
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
## [1.3.0] - 2026-06-23
|
|
24
|
+
|
|
25
|
+
### Added
|
|
26
|
+
- **Business Rule Parser — comprehensive Dataverse-compiled JS pattern coverage** (#37)
|
|
27
|
+
- Pattern G: empty-string check (`(vN) (!==?|===?) ""`) → "is not blank" / "is blank" conditions
|
|
28
|
+
- Pattern H: triple blank check (`((vN)) == undefined && ((vN)) == null && ((vN)) === ""`) collapsed to single "is blank" condition
|
|
29
|
+
- Pattern J: string contains/does-not-contain operations via indexOf-based helper detection
|
|
30
|
+
- Extended patterns A/B/D/E to handle double-paren variables `((vN))` used in complex expressions
|
|
31
|
+
- New `stripOuterParens` helper normalises expression wrapping before pattern matching
|
|
32
|
+
- Added "contains data" triple pre-check in `parseCondition` to collapse 3-part expressions to a single parsed condition
|
|
33
|
+
- **Cascade Configuration in relationship tables** — HTML and Markdown exports (#42)
|
|
34
|
+
- 1:N and N:1 relationship sections now show cascade configuration in collapsible accordion/sub-tables
|
|
35
|
+
- Cascade values displayed: Delete, Merge, Assign, Share, Reparent, Unshare
|
|
36
|
+
- M:N relationships (no cascade — correct)
|
|
37
|
+
- HTML export: `<details>/<summary>` accordion per 1:N/N:1 row; expanded view shows full cascade configuration table with badges and descriptions
|
|
38
|
+
- Markdown export: cascade configuration columns added to 1:N and N:1 relationship tables
|
|
39
|
+
- **Reverse Solution Lookup — `referencingSolutions` field** (#40)
|
|
40
|
+
- New `referencingSolutions?: string[]` field added to all top-level component types: Flow, BusinessRule, WebResource, EntityBlueprint, PluginStep, ClassicWorkflow, BPF, CustomAPI, EnvironmentVariable, ConnectionReference, CanvasApp, CustomPage, ModelDrivenApp
|
|
41
|
+
- Post-processing pass in BlueprintGenerator maps existing `componentToSolutions` inventory to solution unique names and annotates each component (solution-scoped runs only)
|
|
42
|
+
- JSON export: field serialised inline on each component object for programmatic cross-solution analysis
|
|
43
|
+
- HTML export: solution badges in component table rows and business rule expanded views; dedicated "Shared Components" section rendered when any component appears in 2+ solutions
|
|
44
|
+
- Markdown export: "Solutions" column added to Plugins, Flows, Business Rules, and Web Resources summary tables; new `summary/shared-components.md` file generated for solution-scoped runs
|
|
45
|
+
|
|
46
|
+
### Changed
|
|
47
|
+
- **Business Rule Parser debug logging removed** — all debug log statements removed from parsing path; conditional `ppsb-debug` localStorage flag available for development diagnostics
|
|
48
|
+
|
|
49
|
+
### Fixed
|
|
50
|
+
- **HTML export cascade badges** — cascadeBadgeClass CSS class names properly handled (not escaped, as they are code constants)
|
|
51
|
+
|
|
52
|
+
---
|
|
53
|
+
|
|
8
54
|
## [1.1.2] - 2026-03-17
|
|
9
55
|
|
|
10
56
|
### Changed
|
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
> Complete architectural blueprints for your Power Platform solutions.
|
|
4
4
|
|
|
5
|
-
|
|
6
6
|
|
|
7
7
|
|
|
8
8
|
Generate comprehensive technical documentation for Dataverse and Power Platform solutions with automated discovery, analysis, and export capabilities.
|