Fix: Use type alias instead of interface for Props definitions #518
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
This PR changes Props definitions from
interfacetotypealias to align with Vue ecosystem best practices.Changes
export interface Propstoexport type Props = {in:src/components/JsonTreeView.vuesrc/components/JsonTreeViewItem.vueRationale
Type aliases are the recommended approach for Vue props definitions according to Vue's official documentation and the broader Vue community. The main advantages are:
typefor propsColorScheme,ItemData)This addresses feedback from GitHub Copilot's automated review on PR #517.
Testing