Repository navigation
Release 1.1.0: the equation editor and its controls - #66
Merged
Merged
Conversation
The version goes to 1.1.0, the first one with the packages of the editor: SharpEquations.Editing, .Rendering, .Avalonia, .Uno, .Wpf and .WinForms, next to the converter. The public API of the seven packages is now the shipped one: what was in PublicAPI.Unshipped.txt is in PublicAPI.Shipped.txt, so that a later change of it shows. The rules of the two build-time generators are in their AnalyzerReleases.Shipped.md under 1.1.0. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SyVio8afJsGwHW9i5v5HDs
… Uno controls SharpEquations.Editing, .Rendering, .Avalonia and .Uno, and the two Avalonia demos the WebAssembly apps are made of, declare IsAotCompatible on .NET 8 and later, as the converter and the math tools already did: the WebAssembly demos are trimmed and compiled ahead of time, and the analyzers now keep their libraries so. They report nothing in the code as it is. WPF and Windows Forms are left out: neither framework supports trimming. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SyVio8afJsGwHW9i5v5HDs
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merging this to
maintagsv1.1.0and publishes the packages.What changes
BuildVersion.props:VersionPrefix1.0.7 → 1.1.0.PublicAPI.Unshipped.txttoPublicAPI.Shipped.txt, so that a later change of it shows as unshipped. No line is added or removed: only moved, and sorted as the files were.SYSLIB1045ofSharpEquations.RegexPolyfill,XSLT001ofSharpEquations.XsltGenerator) move to theirAnalyzerReleases.Shipped.md, under release 1.1.0.IsAotCompatible, on .NET 8 and later) are turned on where they were missing:SharpEquations.Editing,.Rendering,.Avalonia,.Uno, and the two Avalonia demos the WebAssembly apps are made of. The converter and the math tools had them already. They report nothing in the code as it is. WPF and Windows Forms are left out: neither framework supports trimming.No code changes. The four packages now say they are trimmable and compatible with Native AOT in their metadata.
What 1.1.0 releases
v1.0.7 had the converter only. Since then:
SharpEquations:EquationCommandsandEquationCommand(the control words of UnicodeMath and the commands of LaTeX, for completion). Additions only.SharpEquations.Editing,SharpEquations.Rendering,SharpEquations.Avalonia,SharpEquations.Uno(Uno Platform and WinUI 3),SharpEquations.WpfandSharpEquations.WinForms.Before merging
Microsoft.CodeAnalysis.PublicApiAnalyzersis already referenced by all seven packages, so none was added.Checked
dotnet build SharpEquations.slnx -c Release: 0 warnings, 0 errors, with the analyzers of the public API and of trimming and AOT on. The tests are left to CI.🤖 Generated with Claude Code
https://claude.ai/code/session_01SyVio8afJsGwHW9i5v5HDs