Release v2.2.6#224
Conversation
Add a reusable editor tab settings view and update ted to compose it with its bespoke config settings. Replace matching hardcoded dialog/menu labels with Terminal.Gui resource strings and preserve cancel-before-default button ordering. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Update the brittle edit-menu assertion to follow Terminal.Gui resource labels, and make CI/local cleanup consistently exclude AvaloniaEdit-lifted folders from broad formatting passes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Restore the System.Text using and settings-dialog control flow after rebasing over current develop. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Back-merge v2.2.5 from main into develop
Use Terminal.Gui resource strings in editor chrome
Add NativeAOT publish properties to ted.csproj and extend the release workflow to build platform-specific AOT binaries (linux-x64, osx-arm64, win-x64), upload them as artifacts, and attach them to the GitHub Release on tag pushes. Closes #219 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ifacts feat: include AOT binaries of ted in release artifacts
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Enable GenerateDocumentationFile in the Editor csproj so the XML doc file ships alongside the DLL in lib/net10.0/. This allows DocFX and other documentation tools to extract API summaries from the package. Suppress CS1574/CS1591/CS1723 doc-comment warnings that surface from lifted AvaloniaEdit code and cross-assembly cref references. Add API documentation link to README.md. Closes #222 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…nuget Include XML documentation file in NuGet package
Clarify TextDocument text change event docs
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e435518c0a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| --exclude src/Terminal.Gui.Editor/Folding/ \ | ||
| --exclude src/Terminal.Gui.Editor/Highlighting/ \ |
There was a problem hiding this comment.
Excluding the entire Folding/ and Highlighting/ directories from dotnet format means CI no longer verifies style drift in non-lifted files that live there (for example src/Terminal.Gui.Editor/Folding/IFoldingStrategy.cs, src/Terminal.Gui.Editor/Folding/BraceFoldingStrategy.cs, and src/Terminal.Gui.Editor/Highlighting/XshdRoleMap.cs, which do not carry the AvaloniaEdit adaptation marker). In practice, edits to those files can now merge without either formatter gate catching them, which weakens the maintainability guardrails this workflow is meant to enforce.
Useful? React with 👍 / 👎.
2 participants
Release v2.2.6
Version:
2.2.6NuGet Package:
Terminal.Gui.Editor 2.2.6What happens when this PR is merged
v2.2.6Terminal.Gui.Editor 2.2.6to NuGet.orgmain->developis openedChecklist
2.2.6