refactor: simplify prop usage in Vue components #15
Conversation
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
This change removes unnecessary `props` destructuring in Vue components and directly uses the props where applicable. This improves code readability and consistency across the codebase. No breaking changes are introduced as the functionality remains the same.
|
Thanks @oketafred. Good to know. I'll test it out right now and if everything looks good. I'll approve the PR 👍 |
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.
The Vue 3 documentation recommends not accessing props via props.propName in the template when using <script setup>. Instead, you can directly use the prop name in the template.
No breaking changes are introduced as the functionality remains the same.