You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
10
10
-`project.json` now has a single authoritative JSON schema hosted at `https://www.novamoduletools.com/schema/v{major}/project.json`.
11
11
-`Invoke-NovaBuild` exports the schema to `docs/schema/v{major}/project.json` during build, creating the directory when missing.
12
12
-`nova init` injects `"$schema": "https://www.novamoduletools.com/schema/v{major}/project.json"` into every scaffolded project.
13
+
-`nova init` also writes `.vscode/settings.json` mapping `project.json` to the hosted schema URL so VS Code trusts the remote schema automatically without prompting.
13
14
- VS Code picks up the schema automatically to provide field validation, autocomplete, and hover descriptions while editing `project.json`.
14
15
- The two partial internal schemas (`Schema-Build.json`, `Schema-Pester.json`) are removed; `Schema-Project.json` is the new single source.
15
16
@@ -32,6 +33,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
32
33
- The progress text now stays simple while the bar itself reflects the real test-driven completion state.
33
34
- The configured Pester output still flows live so `project.json` settings such as `Pester.Output.Verbosity = "Detailed"` remain visible.
34
35
- Progress-enabled private workflows now have stronger mirrored progress-contract tests, and the repository adds a guardrail test so future `Write-Progress` workflows cannot land without matching test ownership.
36
+
-`Package.Types` values in `project.json` now report a human-readable validation error in VS Code instead of showing the raw regex pattern. VS Code now shows the accepted values (`NuGet`, `Zip`, `.nupkg`, `.zip`) directly in the error.
Copy file name to clipboardExpand all lines: RELEASE_NOTE.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@ This file summarizes the release notes for NovaModuleTools. **UNRELEASED** chang
7
7
### Added
8
8
9
9
-`nova init` now injects a `"$schema"` property into new projects pointing to the hosted versioned JSON schema, enabling VS Code IntelliSense, autocomplete, and hover descriptions while editing `project.json`.
10
+
-`nova init` also writes `.vscode/settings.json` mapping `project.json` to the schema URL so VS Code trusts it automatically — no manual "Allow" step required.
10
11
11
12
### Changed
12
13
@@ -24,6 +25,7 @@ This file summarizes the release notes for NovaModuleTools. **UNRELEASED** chang
24
25
-`Publish-NovaModule` no longer loses its completion summary after local publish import or CI session refresh steps reload the module.
25
26
-`Test-NovaBuild` and `% nova test` now keep the Nova progress display visibly active during long Pester runs instead of appearing stuck on one step while tests continue.
26
27
- During the long Pester phase, Nova now drives the progress bar from discovered and completed Pester tests instead of elapsed time, keeps the progress text simple, and still shows configured Pester output such as `Pester.Output.Verbosity = "Detailed"`.
28
+
- Invalid `Package.Types` values in `project.json` now show the accepted values (`NuGet`, `Zip`, `.nupkg`, `.zip`) directly in VS Code instead of the raw regex pattern.
`Initialize-NovaModule` creates a new project folder, the standard `src/` layout, and a starter `project.json` file.
28
+
`Initialize-NovaModule` creates a new project folder, the standard `src/` layout, a starter `project.json` file, and a `.vscode/settings.json` entry that maps `project.json` to the versioned JSON schema so VS Code provides IntelliSense without a manual trust prompt.
29
29
30
30
The standard scaffold `project.json` includes Nova's standard Pester defaults, including an opt-in `CodeCoverage` block with `Enabled=false`, common `src/` coverage paths, JaCoCo output in `artifacts/coverage.xml`, and a `90` percent target that can be enabled later.
[Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSUseSingularNouns','', Justification ='VS Code settings is the domain term for the .vscode/settings.json file.')]
[Diagnostics.CodeAnalysis.SuppressMessageAttribute('PSUseShouldProcessForStateChangingFunctions','', Justification ='Private file-writing helper. ShouldProcess is managed at the public Initialize-NovaModule command level.')]
0 commit comments