Skip to content

web assembly color support in dashboard - #135

Merged
Friedrich482 merged 1 commit into
mainfrom
wasm-support
May 25, 2026
Merged

web assembly color support in dashboard#135
Friedrich482 merged 1 commit into
mainfrom
wasm-support

Conversation

@Friedrich482

@Friedrich482 Friedrich482 commented May 25, 2026

Copy link
Copy Markdown
Owner

Commits

  • feat: web assembly

    • added language color for webAssembly in the admin dashboard
    • bumped the extension version
    • updated the version of turbo

Summary by CodeRabbit

  • Chores

    • VSCode extension version updated to 0.0.66
    • Build tool dependencies updated
  • Style

    • WebAssembly syntax highlighting colors updated

Review Change Stack

- added language color  for webAssembly in the admin dashboard
- bumped the extension version
- updated the version of turbo
@coderabbitai

coderabbitai Bot commented May 25, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

This PR applies three independent updates across the repository: a version bump for the VS Code extension to 0.0.66, a turbo build tool dependency upgrade to ^2.9.14, and a language color configuration change replacing webassembly with wat syntax mapping.

Changes

Version and Configuration Updates

Layer / File(s) Summary
VS Code Extension Version Release
apps/vscode-extension/package.json
Extension version incremented from 0.0.65 to 0.0.66 for release.
Build Tool Dependency Update
package.json
Turbo devDependency upgraded from ^2.9.3 to ^2.9.14, capturing newer patch releases.
UI Language Color Mapping
packages/ui/src/colors.json
Language color entry changed from "webassembly" to "wat" with color updated to #6250e7, replacing the previous #04133b mapping.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐰 A little bump here, a dependency there,
Colors now shine with WebAssembly flair,
Turbo runs faster, versions take flight,
Small tweaks and tune-ups to keep code just right! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'feat: web assembly' is vague and generic, using non-descriptive phrasing that doesn't convey the specific changes made in the changeset. Consider a more specific title like 'feat: add WebAssembly language color mapping' or 'feat: add wat language color to dashboard' to clearly describe the primary change.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch wasm-support

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/ui/src/colors.json`:
- Line 701: The "wat" entry was added but we must preserve the old "webassembly"
slug; update the color map so that "webassembly" and "wat" both map to the same
object (i.e., add a "webassembly": { "name": "WebAssembly", "color": "`#6250e7`" }
entry) or implement alias handling in the color lookup to treat "webassembly" as
an alias of "wat" (adjust the lookup code that resolves slugs to check aliases
or fallback to "wat" when "webassembly" is received).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9f5fd5d6-c81c-4b94-9456-8e5a52fa503f

📥 Commits

Reviewing files that changed from the base of the PR and between 7985489 and 1f0f3ec.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (3)
  • apps/vscode-extension/package.json
  • package.json
  • packages/ui/src/colors.json

Comment thread packages/ui/src/colors.json
@Friedrich482
Friedrich482 merged commit 5d86166 into main May 25, 2026
1 check passed
@Friedrich482 Friedrich482 changed the title feat: web assembly web assembly color support in dashboard May 25, 2026
@Friedrich482
Friedrich482 deleted the wasm-support branch May 25, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant