Repository navigation
Releases: gerfen/FluentUI.Blazor.Monaco.EditorPack
Release list
v1.0.0
First stable release. Requires Microsoft.FluentUI.AspNetCore.Components v5 (breaking change from 0.x, which used Fluent UI v4). See UPGRADE_GUIDE_FLUENTUI_V5.md. The v4 line is preserved on the master-4.x branch.
Full Changelog: v0.2.2-preview...v1.0.0
v0.2.2-preview
MonacoMarkdownEditor 0.2.2‑preview — Release Notes
This release introduces a more coherent public API surface, a unified configuration model, and a cleaner initialization pipeline. Because these improvements strengthen long‑term maintainability and developer experience, several breaking changes were made while still in preview.
Adds EditorId to assist with extending the MonacoMarkdownEditor extensibility.
🚨 Breaking Changes
1. New MonacoOptions configuration model
Monaco configuration is now provided through a strongly‑typed options object:
[Parameter]
public MonacoOptions Options { get; set; } = new();This replaces earlier implicit or ad‑hoc Monaco configuration patterns.
Impact:
Consumers must now supply Monaco configuration through the Options parameter.
2. Lifecycle callback renames
| Old Name | New Name |
|---|---|
OnBeforeMonacoCreated |
BeforeCreated |
OnMonacoInitialized |
AfterInitialized |
Impact:
Consumers must update parameter names in Razor components.
3. CSS IntelliSense parameter rename
The previous Css parameter (used for IntelliSense CSS input) has been renamed to:
AdditionalCssThis avoids confusion with the CSS editor component and clarifies its purpose.
Impact:
Consumers must rename Css → AdditionalCss.
4. Internal JS API changes
Two new JS functions were added:
monacoMarkdownEditor.enableFrontMattermonacoMarkdownEditor.setOption
These support the new MonacoOptions model and front‑matter toggle.
Impact:
Consumers who override or wrap the JS module must update their custom scripts.
5. Initialization pipeline changes
The editor now applies Monaco options before calling monacoMarkdownEditor.init.
This ensures:
- Predictable lifecycle ordering
- Consistent editor configuration
- Cleaner separation between configuration and initialization
Impact:
Consumers relying on the old initialization order may need to adjust custom logic.
✨ New Features
Front‑matter support (opt‑in)
Options = new MonacoOptions { EnableFrontMatter = true }This allows the editor to recognize YAML front‑matter blocks and apply appropriate editor behavior.
Unified, Blazor‑first configuration
MonacoOptions provides a clean, discoverable configuration surface:
- Word wrap
- Minimap
- Line numbers
- Font size / font family
ThemeTheming is handled via FluentUI-Blazor Theming infrastructure- Front‑matter toggle
This mirrors the existing MarkdownOptions pattern.
Improved CSS IntelliSense pipeline
CSS input is now clearly separated into:
ExternalCss— aggregated CSS from parent componentsAdditionalCss— CSS provided directly to this component
Both feed into the CSS class harvester for completions and hover support.
🛠 Internal Improvements
- Reorganized parameter groups for clarity and IntelliSense readability
- Cleaner lifecycle flow:
BeforeCreated→ apply options →init→AfterInitialized - Reduced JS surface area while improving extensibility
- More predictable editor state transitions
- Improved naming consistency across components
📦 Summary
0.2.2‑preview represents a significant maturation of the component’s architecture:
- Cleaner API
- Stronger configuration model
- Better lifecycle semantics
- Improved naming
- Clearer CSS IntelliSense inputs
- Front‑matter support
- Minimal but meaningful JS enhancements
These changes position the library for stability as it approaches later preview versions.
v0.2.1-preview
MonacoMarkdownEditor 0.2.1‑preview — Release Notes
This release introduces a more coherent public API surface, a unified configuration model, and a cleaner initialization pipeline. Because these improvements strengthen long‑term maintainability and developer experience, several breaking changes were made while still in preview.
Adds EditorId to assist with extending the MonacoMarkdownEditor extensibility.
🚨 Breaking Changes
1. New MonacoOptions configuration model
Monaco configuration is now provided through a strongly‑typed options object:
[Parameter]
public MonacoOptions Options { get; set; } = new();This replaces earlier implicit or ad‑hoc Monaco configuration patterns.
Impact:
Consumers must now supply Monaco configuration through the Options parameter.
2. Lifecycle callback renames
| Old Name | New Name |
|---|---|
OnBeforeMonacoCreated |
BeforeCreated |
OnMonacoInitialized |
AfterInitialized |
Impact:
Consumers must update parameter names in Razor components.
3. CSS IntelliSense parameter rename
The previous Css parameter (used for IntelliSense CSS input) has been renamed to:
AdditionalCssThis avoids confusion with the CSS editor component and clarifies its purpose.
Impact:
Consumers must rename Css → AdditionalCss.
4. Internal JS API changes
Two new JS functions were added:
monacoMarkdownEditor.enableFrontMattermonacoMarkdownEditor.setOption
These support the new MonacoOptions model and front‑matter toggle.
Impact:
Consumers who override or wrap the JS module must update their custom scripts.
5. Initialization pipeline changes
The editor now applies Monaco options before calling monacoMarkdownEditor.init.
This ensures:
- Predictable lifecycle ordering
- Consistent editor configuration
- Cleaner separation between configuration and initialization
Impact:
Consumers relying on the old initialization order may need to adjust custom logic.
✨ New Features
Front‑matter support (opt‑in)
Options = new MonacoOptions { EnableFrontMatter = true }This allows the editor to recognize YAML front‑matter blocks and apply appropriate editor behavior.
Unified, Blazor‑first configuration
MonacoOptions provides a clean, discoverable configuration surface:
- Word wrap
- Minimap
- Line numbers
- Font size / font family
- Theme
- Front‑matter toggle
This mirrors the existing MarkdownOptions pattern.
Improved CSS IntelliSense pipeline
CSS input is now clearly separated into:
ExternalCss— aggregated CSS from parent componentsAdditionalCss— CSS provided directly to this component
Both feed into the CSS class harvester for completions and hover support.
🛠 Internal Improvements
- Reorganized parameter groups for clarity and IntelliSense readability
- Cleaner lifecycle flow:
BeforeCreated→ apply options →init→AfterInitialized - Reduced JS surface area while improving extensibility
- More predictable editor state transitions
- Improved naming consistency across components
📦 Summary
0.2.1‑preview represents a significant maturation of the component’s architecture:
- Cleaner API
- Stronger configuration model
- Better lifecycle semantics
- Improved naming
- Clearer CSS IntelliSense inputs
- Front‑matter support
- Minimal but meaningful JS enhancements
These changes position the library for stability as it approaches later preview versions.
v0.2.0-preview
MonacoMarkdownEditor 0.2.0‑preview — Release Notes
This release introduces a more coherent public API surface, a unified configuration model, and a cleaner initialization pipeline. Because these improvements strengthen long‑term maintainability and developer experience, several breaking changes were made while still in preview.
🚨 Breaking Changes
1. New MonacoOptions configuration model
Monaco configuration is now provided through a strongly‑typed options object:
[Parameter]
public MonacoOptions Options { get; set; } = new();This replaces earlier implicit or ad‑hoc Monaco configuration patterns.
Impact:
Consumers must now supply Monaco configuration through the Options parameter.
2. Lifecycle callback renames
| Old Name | New Name |
|---|---|
OnBeforeMonacoCreated |
BeforeCreated |
OnMonacoInitialized |
AfterInitialized |
Impact:
Consumers must update parameter names in Razor components.
3. CSS IntelliSense parameter rename
The previous Css parameter (used for IntelliSense CSS input) has been renamed to:
AdditionalCssThis avoids confusion with the CSS editor component and clarifies its purpose.
Impact:
Consumers must rename Css → AdditionalCss.
4. Internal JS API changes
Two new JS functions were added:
monacoMarkdownEditor.enableFrontMattermonacoMarkdownEditor.setOption
These support the new MonacoOptions model and front‑matter toggle.
Impact:
Consumers who override or wrap the JS module must update their custom scripts.
5. Initialization pipeline changes
The editor now applies Monaco options before calling monacoMarkdownEditor.init.
This ensures:
- Predictable lifecycle ordering
- Consistent editor configuration
- Cleaner separation between configuration and initialization
Impact:
Consumers relying on the old initialization order may need to adjust custom logic.
✨ New Features
Front‑matter support (opt‑in)
Options = new MonacoOptions { EnableFrontMatter = true }This allows the editor to recognize YAML front‑matter blocks and apply appropriate editor behavior.
Unified, Blazor‑first configuration
MonacoOptions provides a clean, discoverable configuration surface:
- Word wrap
- Minimap
- Line numbers
- Font size / font family
- Theme
- Front‑matter toggle
This mirrors the existing MarkdownOptions pattern.
Improved CSS IntelliSense pipeline
CSS input is now clearly separated into:
ExternalCss— aggregated CSS from parent componentsAdditionalCss— CSS provided directly to this component
Both feed into the CSS class harvester for completions and hover support.
🛠 Internal Improvements
- Reorganized parameter groups for clarity and IntelliSense readability
- Cleaner lifecycle flow:
BeforeCreated→ apply options →init→AfterInitialized - Reduced JS surface area while improving extensibility
- More predictable editor state transitions
- Improved naming consistency across components
📦 Summary
0.2.0‑preview represents a significant maturation of the component’s architecture:
- Cleaner API
- Stronger configuration model
- Better lifecycle semantics
- Improved naming
- Clearer CSS IntelliSense inputs
- Front‑matter support
- Minimal but meaningful JS enhancements
These changes position the library for stability as it approaches later preview versions.
v0.1.12-preview
- Added support for Monaco lifecycle events
- Added support for setting Markdig options
- Added bUnit test project
- Added unit test project
Full Changelog: v0.1.9-preview...v0.1.12-preview
Download from nuget: https://www.nuget.org/api/v2/package/FluentUI.Blazor.Monaco.EditorPack/0.1.12-preview
Reelease v0.1.9-preview
Refactored samples in a shard RCL, a server demo and a WASM demo. Added a JavaScript module to simplify configuration.
Full Changelog: v0.1.8-preview...v0.1.9-preview
Download from nuget: https://www.nuget.org/api/v2/package/FluentUI.Blazor.Monaco.EditorPack/0.1.9-preview