We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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?
to your account
npm run build
npm run serve
With type definition in production build, bool prop should have value true when passed in with no value (as documented here)
With type definition in production build, bool prop has value "" (empty string) when passed in with no value
This 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 Boolean
The text was updated successfully, but these errors were encountered:
It would be helpful if the repro provided your actually demonstrate the issue.
Sorry, something went wrong.
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 open = ''
open = ''
Work fine, get open=false
Both of these codes works fine in v3.2.19
fix(compiler-sfc): add type for props's properties in prod mode (#4790)
Successfully merging a pull request may close this issue.