-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modelValue set to be optional in FwbInput #343
base: main
Are you sure you want to change the base?
Conversation
WalkthroughThe pull request modifies the Changes
Possibly related PRs
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for sensational-seahorse-8635f8 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/components/FwbInput/FwbInput.vue (1)
64-64
: MakingmodelValue
optional aligns with other components.
This change ensures flexibility by allowing the prop to be omitted if needed. However, consider confirming whether an empty string is the most appropriate default when a numericmodelValue
may be expected.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/components/FwbInput/FwbInput.vue
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: build-pkg (20.x)
Thank you for the PR... I'll test it in the evening in my project and return to you with proper response. |
Hey, Sorry I've drowned in changes for this PR: #344 and wasn't able to take a look at this issue yet.... I'll be back on it before the end of the weekend though ;) |
Starting version 0.1.7 there is a problem with FwbInput component
Seems like it is caused by this PR #327
If
modelValue
has 2 possible types, then is it not optional anymore. It should be marked as optional explicitly in the type definition. I checked modelValue definitions in other components and all of them are optional.Strange thing that I cannot reproduce this issue on the flowbite-vue code base. Only in the project.
Summary by CodeRabbit
modelValue
an optional propertymodelValue
when not explicitly provided