-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
Prop type declaration is not working as expected for Boolean props #4783
Comments
It would be helpful if the repro provided your actually demonstrate the issue. |
My bad, I have updated with link to repository, as well as revising description |
Same issue here. Looks like a regression in production build. This broke us just recently (all our boolean props values suddenly evaluate to false). edit: @LinusBorg I confirm, this is a regression in 3.2.20. I'd mark this as important 🙏 |
Any updates on the related PR getting merged ? |
Not work, get
Work fine, get
Both of these codes works fine in v3.2.19 |
Version
3.2.20
Reproduction link
github.com
Steps to reproduce
npm run build
npm run serve
http://localhost:5000
What is expected?
With type definition in production build,
bool
prop should have valuetrue
when passed in with no value (as documented here)What is actually happening?
With type definition in production build,
bool
prop has value "" (empty string) when passed in with no valueThis issue only happens in production build:
bool
prop is evaluated as empty string when passed in with no value. In development envrionment,bool
prop is properly recognized as a boolean prop.When inspecting production build,
bool
property in props has null value.When refactoring from type declaration to runtime declaration, it works normally. In production build,
bool
property in props has type of BooleanThe text was updated successfully, but these errors were encountered: