test: add Vitest coverage for interface utilities - #286
Open
wyattrspeir-coder wants to merge 1 commit into
Open
Conversation
Adds focused, manifest-derived tests for cn() and getAssetImportTagsFromManifest().
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.
Summary
Adds focused Vitest coverage for
plugins/interface/utils/index.tsxwithout changing production behavior.Covered behavior
cn()combines conditional classes correctly.cn()resolves conflicting Tailwind utilities using the last applicable class.getAssetImportTagsFromManifest()includes the current page's JS entry.vendorandcomponentschunks are included.manifest.json, avoiding brittle hard-coded Vite hashes.Verification
Local simulation performed against the current
plugins/interface/utils/index.tsxlogic and committedpublic/.vite/manifest.json:The upstream repository CI should still be treated as authoritative because this execution environment could not download the repository dependencies directly.
Demo
Short visual walkthrough attached below. It clearly distinguishes the local simulation from authoritative upstream CI.
/claim #71
starbasedb-bounty-71-demo.mp4