Skip to content

Ava Night v1.3.0 — Quality & Readability

Latest
Latest

Choose a tag to compare

View all tags
@Ava-91 Ava-91 released this 02 Sep 17:02
· 1 commit to main since this release
v1.3.0
f4d5aa0

🌙 Ava Night v1.3.0 — Quality & Readability

Ava Night v1.3.0 is a quality-focused release centered on readability, semantic highlighting, Markdown support, Git workflows, validation, and release automation.

This release doesn't radically change the visual identity of Ava Night. Instead, it strengthens the theme underneath the surface: colors now have clearer semantic roles, common editor states are more consistent, Git/diff views are easier to read, and the project has significantly stronger automated validation.

The goal is simple: Ava Night should look calm at midnight without becoming difficult to use when you're actually coding.

✨ Highlights

🎨 Refined semantic highlighting

The semantic token mappings have been audited and expanded to provide a more intentional hierarchy across supported languages.

Mappings now cover roles including:

  • Functions and methods
  • Macros and built-ins
  • Keywords
  • Namespaces and modules
  • Types, classes, interfaces, enums, and enum members
  • Type parameters
  • Strings and regular expressions
  • Decorators and annotations
  • Labels and events
  • Numbers
  • Variables and properties
  • Parameters
  • Operators and modifiers
  • Comments

The intent is to make code structure easier to recognize at a glance without turning the editor into a rainbow.

📝 Better Markdown hierarchy

Markdown received a dedicated syntax pass with expanded fixtures covering:

  • Headings
  • Bold and italic text
  • Strikethrough
  • Links
  • Blockquotes
  • Nested lists
  • Task lists
  • Inline code
  • Fenced code blocks
  • Tables
  • Horizontal rules
  • Embedded HTML

This gives Markdown documents a clearer visual hierarchy while keeping the overall Ava Night aesthetic intact.

🔀 Improved Git, diff, and merge readability

Git-related editor states have been audited and refined.

The theme now provides intentional styling for:

  • Inserted text
  • Removed text
  • Unchanged regions
  • Diff borders
  • Overview-ruler Git markers
  • Merge conflicts
  • Current/incoming merge sections
  • Common merge content

Added, modified, and deleted states remain visually distinct while staying consistent with the rest of the palette.

🌙 More consistent interactive states

Selection, hover, active, and prominent states were refined across the editor UI.

This includes areas such as:

  • Text selection
  • Selection highlights
  • Lists
  • Menus
  • Tabs
  • Command center
  • Status bar items
  • Buttons
  • Extension actions
  • Badges

These states now use intentional child-theme overrides rather than unnecessary duplication of the base palette.

🧪 Stronger automated QA

v1.3.0 significantly expands Ava Night's automated validation.

The test suite now checks:

  • Theme diagnostics
  • Theme quality
  • Required contrast pairs
  • Contrast thresholds
  • Missing colors
  • Fixture inventory
  • Semantic role mappings
  • Semantic role completeness
  • Markdown syntax coverage
  • Git/diff/merge styling
  • Overview-ruler states
  • QA report generation

The current automated contrast suite validates 40/40 required contrast pairs.

The project also maintains syntax fixtures for 15 languages:

  • TypeScript
  • TSX / React
  • JavaScript
  • Python
  • Rust
  • Go
  • C++
  • CSS
  • HTML
  • JSON
  • JSONC
  • Markdown
  • Shell
  • SQL
  • YAML

👀 VS Code smoke testing

A VS Code rendering smoke test is now part of the project's validation workflow.

It packages the extension, installs it into a pinned VS Code runtime, launches VS Code in a headless environment, and verifies that the extension can actually be loaded.

This complements the static validation while keeping the limitation explicit:

Automated tests can validate theme data and extension loading, but they cannot completely replace visual inspection of rendered VS Code pixels.

📦 Release automation

The release process has also been improved.

A published release can now automatically:

  1. Install the required Node.js environment
  2. Validate package and theme metadata
  3. Run diagnostics
  4. Run quality checks
  5. Run the test suite
  6. Package the extension as a VSIX
  7. Upload the VSIX as a release artifact
  8. Attach the packaged VSIX to the GitHub release

This makes future releases more reproducible and reduces the amount of manual release work.

📚 Documentation improvements

The README and syntax-validation documentation were updated to better explain:

  • The Ava Night palette
  • Semantic color roles
  • Supported syntax fixtures
  • Validation commands
  • VS Code smoke testing
  • Release checks
  • The distinction between fixture coverage and complete language support
  • The project's current visual-validation limitations

🎯 Quality & accessibility

A major goal of this release was preserving the theme's dark, low-distraction aesthetic without sacrificing readable contrast.

The validation suite continues to check important editor and UI states against defined contrast thresholds.

The result is a palette that remains intentionally muted while keeping important text, controls, diagnostics, Git states, and interactive elements distinguishable.

🛠️ Validation commands

The repository now provides several focused QA commands:

npm test
npm run diagnostics
npm run quality
npm run qa
npm run vscode:smoke
npm run vsix:smoke
npm run release:check

For the complete QA workflow:

npm run qa

This generates machine-readable and Markdown QA reports under:

tests/results/

📌 Compatibility

Ava Night v1.3.0 targets:

VS Code 1.100.0 and newer

🔄 Upgrade from v1.2.0

If you're already using Ava Night, this release is intended as a straightforward upgrade.

The core midnight palette and visual identity remain familiar, while syntax highlighting, Markdown, Git/diff states, interactive UI states, and project validation have received substantial refinement.

🙏 Feedback

Ava Night is still an evolving theme.

If something looks difficult to read, a syntax category feels visually inconsistent, or a particular VS Code UI state doesn't fit the theme, please report it with enough context to reproduce the issue.

Real-world usage is the next stage of validation.

Ava Night v1.3.0
Where code meets the quiet of midnight. 🌙

Full changelog: v1.2.0 → v1.3.0

Assets 3
Loading